What's the advantage of using a script file (as a task) over using a .bat file registered as an executable (also as a task)?
An executable is a user-created script that lives on the agent. One advantage is that when a job uses an executible, it becomes a requirement for that job and will only go on agents that can access that executible. Also, since an executible is a file it can be centrally maintained as opposed to script tasks which can be anything. For example, suppose you have some workflow where a task needs to open and read a specific file. You could add that logic to the executible file and push it out to all the agents and any task that uses that command would then start using it. Compare that to script tasks where you would have to go out, find all the script tasks that are implementing that workflow and update them one by one.
Script tasks are great for quickly inserting shell commands into a bamboo job. But if you need more centralized control without writing a new task plugin, executibles work well.
Finally, historically all user-defined functionality was controlled through executibles in earlier versions of Bamboo before tasks were ever implemented.
It's officially Tuesday, which means it's officially time for another tip to help you better navigate this space we call the Atlassian Community. 😄 I got a great question from community member, Sa...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs