Reply to post: Re: Could be great

Atlassian: Look at our ginormous Jira revenues!

sed gawk Silver badge

Re: Could be great

Jenkins is okay, provided you do the sane thing and run actual shell scripts from an actual git repo, so the only thing provided by Jenkins is credential/parameter injection.

Ultimately, C/I needs to work in plain shell with the C/I system doing setenv(3). so C/I simply records the value of the previous variable invocations thusly "env > env.txt", allowing local debugging by simply sourcing the env.txt in a clean shell, e.g. env -i sh -c ".env.txt && ./ci-script.sh"

Jenkins just makes this apparent earlier, having played with bamboo, I was curious as to what features caught your eye as they seem fairly interchangeable for me.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon

Biting the hand that feeds IT © 1998–2021