Re: Parameterized Remote Trigger fails with NullPointerException

[Matt Evans]

I have this same issue.  I have three servers setup.  One with Jenkins 
1.609.3, 1.642.4, and 2.60.3.  I can use this plugin on my 1.6 - 1.6 
instances but not 1.6 - 2.0.  Wonder if there is an issue with jenkins 2.0? 
 I also noticed that on my 1.6 > 1.6 instances it returns a 500 if I use 
choice parameters instead of just STRING.  I'm just going to curl the job 
to start it and check the status 
using 
http://jdpgrailsdev.github.io/blog/2015/01/13/jenkins_check_job_status.html

On Tuesday, July 5, 2016 at 12:22:11 PM UTC-7, Jacqueline Taing wrote:
>
> I am trying to use Parameterized Remote Trigger Plugin 
> ,
>  
> but I keep getting error when it tries to launch job:
>
> Remote Jenkins server returned empty response or invalid JSON - but we can 
> still proceed with the remote build.
>
> ERROR: Build step failed with exception
>
> java.lang.NullPointerException 
> 
>
>   at 
> org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.isRemoteJobParameterized(RemoteBuildConfiguration.java:1167)
>  
> 
>
>   at 
> org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.perform(RemoteBuildConfiguration.java:488)
>  
> 
>
>   at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 
> 
>
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:764)
>  
> 
>
>   at hudson.model.Build$BuildExecution.build(Build.java:205) 
> 
>
>   at hudson.model.Build$BuildExecution.doRun(Build.java:162) 
> 
>
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) 
> 
>
>   at hudson.model.Run.execute(Run.java:1744) 
> 
>
>   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 
> 
>
>   at hudson.model.ResourceController.execute(ResourceController.java:98) 
> 
>
>   at hudson.model.Executor.run(Executor.java:374) 
> 
>
> Build step 'Trigger a remote parameterized job' marked build as failure
>
> Finished: FAILURE
>
>
> Has anyone been able to successfully trigger a remote job with this plugin?  
> My remote host configuration uses the Credential plugin with 
> username/password specified.
>
>
> Thanks,
>
> -jacqui
>
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/7fe75c7f-223c-400b-99c8-d69b780c875f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [workflow-plugin] Access to environment variables in flow.groovy

[Matt Evans]

Thanks @Craig, works perfect!


On Tuesday, May 24, 2016 at 4:03:06 PM UTC-7, Craig Rodrigues wrote:
>
> Matt,
>
> Take a look at: 
> https://groups.google.com/d/msg/jenkinsci-users/P7VMQQuMdsY/bHfBDSn9GgAJ
> and see if it helps.
>
> It took me a long time to figure that out, and it was not obvious to me.
>
> --
> Craig
>
>
> On Tue, May 24, 2016 at 3:34 PM, Matt Evans <mev...@parchment.com 
> > wrote:
>
>> I have tried many ways to bring variable in scope to a function, can you 
>> please clarify how the following code should be written to bring the 
>> variable "BRANCH_TEST" in scope?
>>
>> *   def BRANCH_TEST = "master"*
>>
>> *   node {*
>> *   deploy()*
>> *   }*
>>
>> *   def deploy(){*
>> *   echo env.BRANCH_TEST*
>> *   }*
>>
>> Console Output:
>>
>> [Pipeline] echonull
>>
>>
>> On Wednesday, April 1, 2015 at 11:32:06 AM UTC-7, Jesse Glick wrote:
>>>
>>> On Wednesday, April 1, 2015 at 12:55:37 PM UTC-4, Kent Johnson wrote:
>>>>
>>>>  I think I could just echo "$env.BUILD_NUMBER" for those who are 
>>>>> wondering. I didn't test doing so though I am sure it would work.
>>>>
>>>>
>>> Either:
>>>
>>> echo env.BUILD_NUMBER
>>>
>>> or
>>>
>>> echo "${env.BUILD_NUMBER}"
>>>
>>> (Not sure whether Groovy gives higher precedence to `$` or `.` so play 
>>> it safe and use braces if inside a GString.)
>>>
>>> BTW as of the 1.5 release, the live documentation (i.e., Snippet 
>>> Generator) for environment variable handling has been consolidated into the 
>>> help for the new withEnv step, which seemed the most appropriate place for 
>>> it.
>>>
>> -- 
>> 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 jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/fa738334-df6c-48a6-987f-cf4299200cc8%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/fa738334-df6c-48a6-987f-cf4299200cc8%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ddebd5e3-bb17-4605-a6a1-610a90fbaed4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [workflow-plugin] Access to environment variables in flow.groovy

[Matt Evans]

I have tried many ways to bring variable in scope to a function, can you 
please clarify how the following code should be written to bring the 
variable "BRANCH_TEST" in scope?

*   def BRANCH_TEST = "master"*
   
*   node {*
*   deploy()*
*   }*
   
*   def deploy(){*
*   echo env.BRANCH_TEST*
*   }*

Console Output:

[Pipeline] echonull


On Wednesday, April 1, 2015 at 11:32:06 AM UTC-7, Jesse Glick wrote:
>
> On Wednesday, April 1, 2015 at 12:55:37 PM UTC-4, Kent Johnson wrote:
>>
>>  I think I could just echo "$env.BUILD_NUMBER" for those who are 
>>> wondering. I didn't test doing so though I am sure it would work.
>>
>>
> Either:
>
> echo env.BUILD_NUMBER
>
> or
>
> echo "${env.BUILD_NUMBER}"
>
> (Not sure whether Groovy gives higher precedence to `$` or `.` so play it 
> safe and use braces if inside a GString.)
>
> BTW as of the 1.5 release, the live documentation (i.e., Snippet 
> Generator) for environment variable handling has been consolidated into the 
> help for the new withEnv step, which seemed the most appropriate place for 
> it.
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/fa738334-df6c-48a6-987f-cf4299200cc8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins no longer detects changes when job is setup to build multiple branches

[Matt Evans]

Recently we changed our way of building branches.  We use GIT and have scm 
polling to build branches.  First, we used to poll a specific branch name 
(release/1.0).  Now we use a regex (release/*).  For example, instead of 
having:


jenkinsJob1 that builds branch release/1.0 

jenkinsJob2 that builds branch release/2.0


Now we only have one job:


jenkinsJob that builds release/* (so release/1.0 and release/2.0 are both 
built by job)


However, the new commits don’t show as changes anymore (when I click 
changes summary is blank).  It now only shows revision and branch name when 
clicking on build number.  This causes our developers to get confused 
because they're used to seeing their commit messages.  I assume this 
behavior is because the previous build was built from different branch and 
so it can’t aggregate changes.  Is this the case and is there a workaround?

Thanks!

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/4e729e15-2c84-453a-a9e1-3c49619572ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.