On Monday, April 20, 2015 at 6:47:13 AM UTC-4, Tom Deblauwe wrote:
>
> I get a notification from Stash with a commit id from the "project.git"
> repository(as expected), but jenkins tries to checkout that commit in the
> "workflows.git" repository, NOT the "project.git" repository.
>
I think the
Tom,
I am working out the same sort of thing with Jenkins Workflows and GitLab.
It was very simple to get working for me.
All I had to do was
1. make a new workflow job,
2. check the "Trigger builds remotely" box
3. set an authentication token
4. Go to my repository settings in git
Hello again,
Just for the record: I solved it now by putting my jobs under the workflows
git repo, so in a directory like this:
"src/com/bla/jobs/BuildApplication.groovy" and then in that script I could
make a "start()" function and then call that in the job like this:
def task = new com.bla.j
Hello,
It seems one (not so good) solution is to disable giving the SHA1 to
jenkins in the hook on the Stash server that notifies Jenkins. There is an
option you can disable so that the SHA1 is not given when triggering the
corresponding jenkins job. Not optimal because Stash is not in control
Hello,
I am using the "groovy CPS DSL from SCM" as my configuration for my
workflow. This works well and reads the scripts from my "workflows.git"
reposity.
In the workflow script itself, I start with:
node {
git branch: '**', changelog: false, poll: true, url:
'ssh://git@stash:7999/my/pro
