It is quite common that a script which works on a developer desktop does not work in another environment like Jenkins.
Common reasons include: - Scripts assuming they are running with a controlling terminal - Scripts assuming the existence of specific ssh private keys - Scripts assuming the existence of specific environment variables - Scripts assuming a specific user account name - Scripts assuming specific versions of tools are available - Scripts assuming specific execution environment (Windows, Linux, FreeBSD, macOS, etc.) One way to diagnose those types of dependencies is to create a new account on your development computer and run the script from that new account. Another technique is to create a new account on a Jenkins agent computer and run the script from there. Another technique is to run the script from a cron or batch job as yourself. Mark Waite On Tue, Feb 11, 2020 at 5:06 PM Sai Pavwan <[email protected]> wrote: > Hi , > I am on my jenkins which is hosted on ECS cluster. I have created a > jenkins job and planned to run that job for every release. So coming to the > point this script will transition jira tickets, will change the jira > tickets status. The process of picking jira tickets will be filtered by > commit messages between git branches. I am using a command git log > origin/master..${BRANCH} --oneline --no-merges this will give you all the > commit messages which will include Jira Ticket numbers. From that messages > I am using sed command and regular expressions concepts to take out the > ticket number like X1-(0-9). This extracted number will be passed to a Jira > Query to transition ticket automatically. > So the thing is I developed this script in local system which > works fine and it transitioning all the tickets like around 200 tickets for > every release, so when i add this script to Jenkins job in Build --> > Execute Shell its not working as expected. There is not fail in job but the > response was absolutely wrong , if we have a 100 tickets in branch every > time its getting only one ticket number out from the Repo's. Just because > its working in my local and its working in Jenkins just want to make sure > whether this problem is with the Jenkins or i am missing anything. Can you > guys please help me out on this. Thanks in advance. > - Pavwan. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/1be64daa-3235-4c49-9d05-501e8e31ddda%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/1be64daa-3235-4c49-9d05-501e8e31ddda%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF-SsixFJbq7Xxbj1OVxsuDdHJ24%2Bqy6BbeBdRt7ZKsow%40mail.gmail.com.
