movingblocks / groovyjenkins Goto Github PK

There is a fairly simple way to decorate the Jenkins job log with an active link to a just-triggered job.

ProvisionBuilder gets the link for free as it uses the normal routine of triggering builds as a post-build action. RetireBuilders for instance doesn't, as it pulls up DestroyDropletAgent via Groovy method. There may be a different way to instead trigger jobs normally but with a condition in place.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/9644154-add-in-links-to-groovy-triggered-jobs?utm_campaign=plugin&utm_content=tracker%2F2774565&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F2774565&utm_medium=issues&utm_source=github).

Make a job with Chef Identity active, preparing the build environment. The .chef dir gets created and has the knife.rb file in it correctly, yay!

Now enable Git for the job, to pull in any repo. Wipe the workspace. The Git clone works fine and the .git dir gets created. The .chef dir no longer appears. Cheffy stuff fails. Wat.

It seems inconsistent and works sometimes, fails sometimes ...

There is a workaround - run the job once with only Chef enabled, not Git. The .chef is created. Then enable Git and .git is created. I suspect though that any actual changes to the knife.rb template in Configure Jenkins will fail to replicate in the .chef dir, which would be awfully easy to forget and pull out hair over for a few hours.

Edit: Seems so inconsistent the workaround doesn't work well enough either :( Disabled Git for the DestroyDropletAgent job too

Need to file a bug against the Chef Identity plugin.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/9643796-chef-identity-plugin-for-jenkins-doesn-t-work-when-git-also-active?utm_campaign=plugin&utm_content=tracker%2F2774565&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F2774565&utm_medium=issues&utm_source=github).

Unlike Groovy System script steps done as part of the main build the Post-Build Groovy step used by ProvisionBuilder job doesn't give an obvious option to run via script file instead of copy-pasted script :-(

Thus the FindAndForwardDropletInfo.groovy script hosted here has to be manually copy pasted each time it is changed, or an awkward automation step needs to do it outside standard process.

Maybe there's a way to do it better, like wrapping the script in a jar, putting that on the classpath (an option in the post-build step), and calling it from a tiny script snippet

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/9643723-find-way-to-source-scripts-for-post-build-groovy-steps-via-git?utm_campaign=plugin&utm_content=tracker%2F2774565&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F2774565&utm_medium=issues&utm_source=github).