Re: Job properties are not (should be !?) cumulative

[harold . putman]

Yes it is working as designed. 
https://jenkins.io/doc/pipeline/steps/workflow-multibranch/#properties-set-job-properties
"Note that any existing properties of the job will be replaced with the 
list given here."

It would be nice to be able to modify job properties rather than overwrite 
everything. It makes for a confusing user experience when you set job 
properties manually, and then have them blown away when your pipeline job 
runs. 

I've been working around it by first reading the properties I want to 
preserve and then writing them back, but this is ugly and very undocumented.


On Friday, May 19, 2017 at 4:28:12 AM UTC-4, nco...@lbisa.com wrote:
>
> Project properties are not cumulative when additional settings are set 
> during the pipeline.
>
>
> For example, if setting a Parameterized build and later in the pipeline, 
> a Discard Old Builds is set, the Parameterized build is unset.
>
> I had this happening when the Discard Old Builds were used in a Shared 
> library, later in the pipeline.
>
>
> When a additional propertie is set, it shouldn't unset all the previous 
> properties, if they are not the same type (discard builds vs parameters).
>
>
> Someone know if this is working as designed or is something that could be 
> implemented?
>

-- 
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/167f7cb9-64fd-4f85-b473-0cde1f7613e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: AWS EC2 API Plugin

[harold . putman]

Check https://plugins.jenkins.io/

On Monday, April 24, 2017 at 11:00:20 AM UTC-4, Johnathan Kanarek wrote:
>
> Hi,
>
> I need to create images, run instances, start instances and stop instances 
> during build.
>
> Is there an existing plugin that enable AWS EC2 APIs as build steps?
>
> I don’t mind creating one by myself, but prefer to use existing one.
>
>  
>
> Johnathan.
>

-- 
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/7ab45983-2ab3-4ab5-8b4b-aecc04ff4d76%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help me with this error

[harold . putman]

Is Git properly installed on your Jenkins server?

https://support.cloudbees.com/hc/en-us/articles/218156697-Git-Failed-to-connect-to-repository-Could-not-init-tmp

On Wednesday, January 11, 2017 at 7:19:44 AM UTC-5, Sathish M wrote:
>
>
> Failed to connect to repository : Error performing command:  ls-remote -h 
> g...@github.com :
>
>
> and 
>
>
>
> Started by user Administrator 
> Building on master in workspace C:\Users\User\.jenkins\workspace\test-git
> Cloning the remote Git repository
> Cloning repository g...@github.com:/ant_1
>  >  init C:\Users\User\.jenkins\workspace\test-git # timeout=10
> ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException 
> :
>  Could not init C:\Users\User\.jenkins\workspace\test-git
>   at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:666)
>  
> 
>   at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:467)
>  
> 
>   at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1054) 
> 
>   at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1094) 
> 
>   at hudson.scm.SCM.checkout(SCM.java:495) 
> 
>   at hudson.model.AbstractProject.checkout(AbstractProject.java:1278) 
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
>  
> 
>   at 
> jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) 
> 
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) 
> 
>   at hudson.model.Run.execute(Run.java:1720) 
> 
>   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 
> 
>   at hudson.model.ResourceController.execute(ResourceController.java:98) 
> 
>   at hudson.model.Executor.run(Executor.java:404) 
> 
>
>

-- 
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/be631749-8b2c-49c3-9c40-7500f3fa403d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Blue Ocean Parameters

[harold . putman]

I have a pipeline build that uses the ExtendedChoice plugin to let a user 
choose which profiles to build from a multimodule maven project.

[ ] Everything
[ ] UI
[ ] Backend
[ ] Admin tools

Blue Ocean does not prompt for parameters when the build is Run, so I 
assume I need to prompt for input. I'm having difficult figuring out the 
magic to allow checkboxes for input. I'm looking at the documentation here 
https://jenkins.io/doc/pipeline/steps/pipeline-input-step/#input-wait-for-interactive-input,
 
but it doesn't provide much help. Are there any examples of different types 
of input?

Here are two inputs that I was able to get working...

def userInput = input(
 id: 'userInput', message: 'Let\'s promote?', parameters: [
 [$class: 'TextParameterDefinition', defaultValue: 'uat', description: 
'Environment', name: 'env'],
 [$class: 'BooleanParameterDefinition', defaultValue: true, description: 
'Target', name: 'target']
]) 

Can anyone point me to others that might support checkboxes?

-- 
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/bd7025d4-b833-4712-a165-ddd784e6c9cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Parsing XML with Pipeline script

[harold . putman]

I was trying to parse and XML file with XmlSlurper like described here 
(http://groovy-lang.org/processing-xml.html)

def text = '''


Groovy


'''

def list = new XmlSlurper().parseText(text) 

println list.technology.name.text()

Using a GPath expression like this list.technology.name.text() works fine 
but requires an admin to allow "method groovy.lang.GroovyObject getProperty 
java.lang.String" which the script security plugin recommends against 
("Approving this signature may introduce a security vulnerability! You are 
advised to deny it."). Since I am not the owner of the Jenkins instance, I 
am not sure I can convince them this is OK to approve. 

Is there a way to write the code such that it does not depend on 
GroovyObject.getProperty being permitted? Or is there someway to configure 
Jenkins so that this can work?



-- 
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/648ea072-7465-4bfb-8254-ea870e1801b3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.