Skip to content

Commit 0dcefdd

Browse files
committed
Fix typo in readme.
1 parent 0e4e9c2 commit 0dcefdd

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
After making commits to Stash, this plugin will make a Http POST request to a specified URL, adding in query parameters for the Source Ref and Source Sha. This plugin listens to both the main repository and all pull-requests.
88

99
##Background
10-
While attempting to migrate source control to stash and and build to jenkins I noticed that there wasn't a good way of having Stash be the source of truth and Jenkins build on time for every commit. There were a bunch of Stash plugins some which could listen for Forked-repository pull requests and some that would send commit information. The Jenkins Post-Receive plugin for Stash did everything correct except attempt to start Jenkins polling. Jenkins polling is useless, and I am not sure what problem it solves. I want to build every commit and every pull-request, and I thought it wasn't a problem that would be hard to solve. Fortunately if you pass a sha as the branch (the Jenkins GIT Plugin GIT_BRANCH parameter), the plugin confusingly enough will build that sha in a detached mode. The only explanation I have for this is that git supports that functionality innately, so the plugin does too.
10+
While attempting to migrate source control to stash and and build to jenkins I noticed that there wasn't a good way of having Stash be the source of truth and Jenkins build one time for every commit. In essence having Jenkins work like Travis-CI. There were a bunch of Stash plugins some which could listen for Forked-repository pull requests and some that would send commit information. The Jenkins Post-Receive plugin for Stash did everything correct except attempt to start Jenkins polling. Jenkins polling is useless, and I am not sure what problem it solves. I want to build every commit and every pull-request, and I thought it wasn't a problem that would be hard to solve. Fortunately if you pass a sha as the branch (the Jenkins GIT Plugin GIT_BRANCH parameter), the plugin confusingly enough will build that sha in a detached mode. The only explanation I have for this is that git supports that functionality innately, so the plugin does too.
1111

1212
But that still left me with one small problem of how to send the commit information to Jenkins, for which no current Stash plugin was smart enough to handle that task. There lies the origin of this plugin. Although this could be used with any repository, an example for Jenkins would be having a url as:
1313
http://jenkins/job/JENKINS_JOB_NAME/buildwithparameters?token=TOKEN

0 commit comments

Comments
 (0)