Okay, i fixed it for myself. One of the intermediate steps failed for me.
I was trying to archive the jar file from a different folder than what I
config'ed. Apparently, its something to deal with the work space area
(either we delete the workspace or something been changed)
On Sat, Dec 10,
Exactly in the same position.. trying to find a solution
-Prabhu
On Friday, August 12, 2016 at 5:46:03 AM UTC-7, thomas@teamaol.com
wrote:
>
> All parts of the script are like this:
>
> try {
>// do something
> } catch(all) {
> def message=""
> notifySlack(message)
>
That would be done on the Travis side, so you'd have to figure that out
under Travis.
On Sat, Dec 10, 2016, 10:47 wrote:
> Hi,
>
> Thanks for the info.
> I want to know how to fetch the parameter of GitHub Committer email id in
> GitHub Repository code. So that I can
You can use the "Replay" option, which might help you iterate a little bit
faster. There isn't really a good way to test and validate that your
pipeline is correct other than just running it.
https://issues.jenkins-ci.org/browse/JENKINS-33925 is open for a test
framework for Jenkinsfile.
On Fri,
Hi,
Thanks for the info.
Can you please let me know how to fetch the parameter of GitHub Committer
email id in GitHub Repository code. So that I can pass the committer email
id parameter into my Jenkins Job-parameterized build.
Thanks,
Ajay.
--
You received this message because you are
Hi,
Thanks for the info.
I want to know how to fetch the parameter of GitHub Committer email id in
GitHub Repository code. So that I can pass the committer email id parameter
into my jenkins Job-parameterized build.
Thanks,
Ajay.
2016 at 3:42:28 PM UTC-8, slide wrote:Aj
On Thursday, December
Comments are inline
On Thu, Dec 8, 2016 at 9:20 AM Mike Neary wrote:
> I have a project that poll's Git every 5 minutes and builds on changes
> using the Git plugin in a pipeline job. The issue I'm having is that if
> the build fails (inside of 5 minutes), the next poll