Re: Jenkins Publish Over SSH for Jenkins Pipeline

2016-08-11 Thread ctime800
It works.  Now, does this mean the Publish Over SSH needs to support 
Jenkins pipeline for this to work?  Thanks.


On Thursday, August 11, 2016 at 1:37:52 PM UTC-7, Baptiste Mathus wrote:
>
> You can simply use a plain ssh or scp call through an sh step, wrapped in 
> an sshagent step.
>
> Cheers
>
> Le 11 août 2016 8:31 AM, "ctime800"  a 
> écrit :
>
>> I need to use the Jenkins Publish over ssh plugin in the Jenkins 
>> pipeline.  What would be the syntax for this?  I tried to use the script 
>> generator but this one is not in the list.  Please advise.  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-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/ca946069-baed-4059-8ccb-60d15e84d239%40googlegroups.com
>>  
>> 
>> .
>> 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/451baa30-0b10-405b-806f-30ae9711e494%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Error on Windows Slaves

2016-08-11 Thread Sajith Majeed- Saaj
This appears to be resolved now. Space could have been an issues as we did
nothing from our end.

On Thu, Aug 11, 2016 at 2:15 AM,  wrote:

> Can you check if you have write permissions under 
> e:\jenkins\workspace\Jobfolder
> folder?
>
> Also can you share the full log?
>
> On Thursday, 11 August 2016 04:17:17 UTC+5:30, Sajith Majeed - Saaj wrote:
>>
>> We started receiving the below error from yesterday on our windows
>> slaves. This was working until yesterday and started to happen all of a
>> sudden. Have anyone seen this error and help us with some inputs on this?
>>
>>
>> java.io.IOException: remote file operation failed: 
>> e:\jenkins\workspace\Jobfolder
>>  at hudson.remoting.Channel@3c3e8ed5:WINDOWSHOST: java.io.IOException: The 
>> filename, directory name, or volume label syntax is incorrect
>>
>>
>>
>>
>> Thanks | Sajith
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-users/GTlQHf-TkuE/unsubscribe.
> To unsubscribe from this group and all its topics, 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/f4b639bd-ffa8-49d4-869a-247bc6bbb71b%40googlegroups.
> com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Thx | Saaj | 469 571 3365*

-- 
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/CABf58KhE4mM3p4zV-wFtHbYtMbWOhdFrfK82hNckvYk7ky9-DQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Automated Jenkins Plugin/Dependency Management

2016-08-11 Thread Michael Kobit
We are looking at doing something similar (actually talking about this with 
colleagues today). The idea is to basically build an immutable Jenkins 
instance that can't be modified. Or at least severely limit any kinds of 
modifications to it so that we have an easily deployable "Jenkins as a 
service".

I've looked at possibly doing an "unpack and install" execution with the 
*jenkins.war 
*, but it doesn't look like an easy route. The other pain-point I see is 
effectively treating the correct files as "data" that should be persisted 
over time, rather than at "Jenkins build time". I am considering trying out 
the Docker-type approach. I think for plugin resolution, we are probably 
going to have to go the route that you are talking about for doing the 
resolution ourselves.

For security type issues, I think we could still handle it with the Docker 
approach. Build whatever restrictions into the next "immutable" image and 
making that deployable. Then, we can have a "staging" area and easily 
rollback if we effectively control all the things we need to control. We 
are experimenting with pipelines right now, and are waiting to see 
how https://issues.jenkins-ci.org/browse/JENKINS-33507 will work for us to 
get as much of the job configuration out of Jenkins as possible.

We are still in the brainstorming phase, so I'm interested to see who else 
has ran into this and what they have done.

On Thursday, August 11, 2016 at 5:47:45 PM UTC-5, Jason Kulatunga wrote:
>
> Hey,
> Thanks for all the feedback :)
>
> @Daniel Beck:
> Yup, I'm familiar with the limitations of the 
> https://updates.jenkins-ci.org/current/update-center.json file. Thats why 
> I'm thinking of creating a plugin/dependency resolution system that will 
> have to directly download the specific version of a plugin file from update 
> site folder structure https://updates.jenkins-ci.org/download/plugins/*/ or 
> use https://updates.jenkins-ci.org/latest/ if no version restriction is 
> found.
>
> I wasn't aware that pinning was pointless in 2.x so that'll be an 
> interesting problem to deal with. It seems that I'll have to restrict all 
> access to the UpdateCenter for idea #1, or do a hybrid approach with a 
> UpdateCenter subclass as well.
>
> @Baptiste Mathus 
> Unfortunately just using an image with locked plugins isn't a long term 
> solution, because we'll have to occasionally update our Jenkins due to 
> required security updates in plugins or the main application. So being able 
> to update plugins, creating a new *.lock file, test the plugin interactions 
> and deploying the *.lock file to existing Jenkins servers is a requirement. 
>
> I was hoping to stay away from a hybrid approach that used both an 
> executable and a subclass as it makes development and deployment more 
> complicated, decreasing adoption with Jenkins users. 
>
> Honestly the goal was to create a tool like Bundler/Pip which would just 
> work out of the box for 99% of use cases. 
>
> Are there other people experiencing the same issue? I'm more than happy to 
> create my own open source solution, but I'd love to base it on an existing 
> (even unmaintained) project. 
>
> -Jason
>
>
> On Thursday, August 11, 2016 at 4:51:07 PM UTC-4, Baptiste Mathus wrote:
>>
>> IMO a Docker image with the right set of plugins you've tested, plus the 
>> security config you're talking about about forbidding any upgrade would 
>> seem a simpler way. And probably it would your life simpler if you somehow 
>> have to support all those different instances which can currently be 
>> actually quite different.
>>
>> HTH
>>
>> Le 11 août 2016 3:14 PM, "Jason Kulatunga"  a écrit :
>>
>> Hey Jenkins-Users,
>>
>> I manage almost a dozen Jenkins servers and our team has been having some 
>> issues with plugin management: such as locking our new installations to 
>> known working versions of some troublesome Jenkins plugins.
>> We use chef + Jenkins DSL to completely automate the initial installation 
>> of Jenkins, but we're not exactly thrilled with the way the Chef cookbook 
>> handles plugin installation and we've also verified that 
>> 'installNecessaryPlugins' does not actually respect the version parameter. 
>>
>> curl -XPOST 
>> http://192.150.23.105:8080/pluginManager/installNecessaryPlugins -d 
>> ''
>>
>> As such I've started looking into alternative means of locking plugins in 
>> an automated way during installation and I've come up with the following 
>> ideas:
>>
>> # An External Dependency Management Tool, eg Bundler, Pip, Berkshelf
>> Basically an executable that would:
>>
>>1. retrieve a list of all plugins installed in a specific Jenkins 
>>server using the API, and add them to a dependency graph (with metadata: 
>>installed, pinned, enabled, version)
>>2. look for a dependency config file (like Gemfile, Berksfile, 
>>requirements.txt)
>>3. iterate through all the uninstalled plugins in the dep config file 
>>and add them 

Re: Automated Jenkins Plugin/Dependency Management

2016-08-11 Thread Jason Kulatunga
Hey,
Thanks for all the feedback :)

@Daniel Beck:
Yup, I'm familiar with the limitations of the 
https://updates.jenkins-ci.org/current/update-center.json file. Thats why 
I'm thinking of creating a plugin/dependency resolution system that will 
have to directly download the specific version of a plugin file from update 
site folder structure https://updates.jenkins-ci.org/download/plugins/*/ or 
use https://updates.jenkins-ci.org/latest/ if no version restriction is 
found.

I wasn't aware that pinning was pointless in 2.x so that'll be an 
interesting problem to deal with. It seems that I'll have to restrict all 
access to the UpdateCenter for idea #1, or do a hybrid approach with a 
UpdateCenter subclass as well.

@Baptiste Mathus 
Unfortunately just using an image with locked plugins isn't a long term 
solution, because we'll have to occasionally update our Jenkins due to 
required security updates in plugins or the main application. So being able 
to update plugins, creating a new *.lock file, test the plugin interactions 
and deploying the *.lock file to existing Jenkins servers is a requirement. 

I was hoping to stay away from a hybrid approach that used both an 
executable and a subclass as it makes development and deployment more 
complicated, decreasing adoption with Jenkins users. 

Honestly the goal was to create a tool like Bundler/Pip which would just 
work out of the box for 99% of use cases. 

Are there other people experiencing the same issue? I'm more than happy to 
create my own open source solution, but I'd love to base it on an existing 
(even unmaintained) project. 

-Jason


On Thursday, August 11, 2016 at 4:51:07 PM UTC-4, Baptiste Mathus wrote:
>
> IMO a Docker image with the right set of plugins you've tested, plus the 
> security config you're talking about about forbidding any upgrade would 
> seem a simpler way. And probably it would your life simpler if you somehow 
> have to support all those different instances which can currently be 
> actually quite different.
>
> HTH
>
> Le 11 août 2016 3:14 PM, "Jason Kulatunga"  > a écrit :
>
> Hey Jenkins-Users,
>
> I manage almost a dozen Jenkins servers and our team has been having some 
> issues with plugin management: such as locking our new installations to 
> known working versions of some troublesome Jenkins plugins.
> We use chef + Jenkins DSL to completely automate the initial installation 
> of Jenkins, but we're not exactly thrilled with the way the Chef cookbook 
> handles plugin installation and we've also verified that 
> 'installNecessaryPlugins' does not actually respect the version parameter. 
>
> curl -XPOST 
> http://192.150.23.105:8080/pluginManager/installNecessaryPlugins -d 
> ''
>
> As such I've started looking into alternative means of locking plugins in 
> an automated way during installation and I've come up with the following 
> ideas:
>
> # An External Dependency Management Tool, eg Bundler, Pip, Berkshelf
> Basically an executable that would:
>
>1. retrieve a list of all plugins installed in a specific Jenkins 
>server using the API, and add them to a dependency graph (with metadata: 
>installed, pinned, enabled, version)
>2. look for a dependency config file (like Gemfile, Berksfile, 
>requirements.txt)
>3. iterate through all the uninstalled plugins in the dep config file 
>and add them (and their dependencies) to the dependency graph
>4. solve the graph by ensuring that no pinned/locked version conflicts 
>occur. 
>5. download all uninstalled plugins directly from 
>https://updates.jenkins-ci.org/
>6. using the Jenkins api, pin any version locked plugins specified in 
>the dependency config file. 
>7. write the solved dependency graph to the filesystem (eg 
>Berksfile.lock, Gemfile.lock) (and use it for any subsequent installs if 
> no 
>plugins have changed)
>8. disable all permissions to the update center in Jenkins so no users 
>enable/update plugins manually. 
>
> # UpdateCenter Override
>
>1. subclass the default Jenkins UpdateCenter, and tell Jenkins to use 
>it using a JVM property
>2. override the UpdateCenter.InstallationJob constructor to download 
>the plugin version specified from the  dependency config lock file if it 
>exists or install like normal and then generate/update a dependency config 
>lock file with every operation.
>3. listen to the pin event in the PluginCenter and update the 
>dependency config lock file. 
>
> I'm not sure if anyone has done something similar but I wanted to get some 
> feedback before I spent too much time investigating either idea. 
>
> Any and all feedback is welcome
>
> -Jason
> Build Automation Engineer
> Adobe
>
>
>
>
> -- 
> 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 

Re: Blocking Pipeline builds while Up- and Downstream Dependencies are building

2016-08-11 Thread 'StuporMundi' via Jenkins Users
Hi,

sorry, I probably should have described it more precise...
I do in fact have my pipeline set up the way you suggested it: There's a 
stage for the build (on different platforms, potentially in parallel), 
there's a stage for the tests (again on different platforms) and there is a 
deployment stage that copies the relevant files to a file server if the 
previous stages did end successfully.

However, the complete product consists of a few dozen shared objects and 
executables, several documentation files to go with them and of course the 
installer packages. So I have a total of about 300 jenkins projects 
configured on our build server. These are currently either matrix or 
freestyle projects - but even though I made an effort to centralize as many 
parts of the projects as possible, the whole setup is not as flexible as 
I'd like it to be as changes/improvements to the build scripts are 
time-consuming to apply to so many projects, which is why I'd gladly switch 
to scripted pipelines. But of course I wouldn't want to e.g. have one of 
the documentation builders to overwrite a pdf file while it is being 
packaged into an installer by one of the installer builders. So the 
synchronization mechanism that the two aforementioned options offer on the 
freestyle projects are as far as I can see an essential feature for the 
setup I am maintaining.

That's why I am looking for a way to get the same feature on a pipeline...

-- 
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/27651ae7-40fd-4307-ac81-0a7e5106d4c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Automated Jenkins Plugin/Dependency Management

2016-08-11 Thread Baptiste Mathus
IMO a Docker image with the right set of plugins you've tested, plus the
security config you're talking about about forbidding any upgrade would
seem a simpler way. And probably it would your life simpler if you somehow
have to support all those different instances which can currently be
actually quite different.

HTH

Le 11 août 2016 3:14 PM, "Jason Kulatunga"  a écrit :

Hey Jenkins-Users,

I manage almost a dozen Jenkins servers and our team has been having some
issues with plugin management: such as locking our new installations to
known working versions of some troublesome Jenkins plugins.
We use chef + Jenkins DSL to completely automate the initial installation
of Jenkins, but we're not exactly thrilled with the way the Chef cookbook
handles plugin installation and we've also verified that
'installNecessaryPlugins' does not actually respect the version parameter.

curl -XPOST http://192.150.23.105:8080/pluginManager/installNecessaryPlugins
-d ''

As such I've started looking into alternative means of locking plugins in
an automated way during installation and I've come up with the following
ideas:

# An External Dependency Management Tool, eg Bundler, Pip, Berkshelf
Basically an executable that would:

   1. retrieve a list of all plugins installed in a specific Jenkins server
   using the API, and add them to a dependency graph (with metadata:
   installed, pinned, enabled, version)
   2. look for a dependency config file (like Gemfile, Berksfile,
   requirements.txt)
   3. iterate through all the uninstalled plugins in the dep config file
   and add them (and their dependencies) to the dependency graph
   4. solve the graph by ensuring that no pinned/locked version conflicts
   occur.
   5. download all uninstalled plugins directly from
   https://updates.jenkins-ci.org/ 
   6. using the Jenkins api, pin any version locked plugins specified in
   the dependency config file.
   7. write the solved dependency graph to the filesystem (eg
   Berksfile.lock, Gemfile.lock) (and use it for any subsequent installs if no
   plugins have changed)
   8. disable all permissions to the update center in Jenkins so no users
   enable/update plugins manually.

# UpdateCenter Override

   1. subclass the default Jenkins UpdateCenter, and tell Jenkins to use it
   using a JVM property
   2. override the UpdateCenter.InstallationJob constructor to download the
   plugin version specified from the  dependency config lock file if it exists
   or install like normal and then generate/update a dependency config lock
   file with every operation.
   3. listen to the pin event in the PluginCenter and update the dependency
   config lock file.

I'm not sure if anyone has done something similar but I wanted to get some
feedback before I spent too much time investigating either idea.

Any and all feedback is welcome

-Jason
Build Automation Engineer
Adobe




-- 
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/2d4f0e32-7d6a-4159-9635-51df7ff83643%40googlegroups.
com

.
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/CANWgJS54gzCcyVtMd1z4UXGmdeLoNccqJm3G4tU3pOmOKWALQA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Organizing artifacts?

2016-08-11 Thread Baptiste Mathus
I don't think it's currently possible, nor do I know of a plugin doing that
of the top of my head. So possibly file a Jira issue with your use case.
And ideally try and propose some impl by yourself if you wanna see it
forward more quickly.

My 2 cents

Le 11 août 2016 4:55 PM, "Arnaud bourree"  a
écrit :

> +1
>
> 2016-08-11 14:51 GMT+02:00 Jonathan Hodgson :
>
>> Hi,
>>
>> I'm winding up with quite a lot of artifacts, logs, built code, test
>> results etc.
>>
>> Is there a way that I could organize these so that it's not just a flat
>> list on the build page?
>>
>> regards
>>
>> Jon
>>
>> --
>> 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/ms
>> gid/jenkinsci-users/1450a2e1-4824-4439-8207-352ac33805ce%
>> 40googlegroups.com
>> 
>> .
>> 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/CAESUf_AD_NHZjW_nhNBGdKLPg6wbfu7gyC%
> 3DBSZzGVLOnDZRo9w%40mail.gmail.com
> 
> .
> 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/CANWgJS5c0hHfK8FDj_QH%3DWgWT4rt5k%2BNA%2BaTTLDO__R7LA4TFQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Blocking Pipeline builds while Up- and Downstream Dependencies are building

2016-08-11 Thread Baptiste Mathus
Though I think it should still be feasible, the fact you don't much
reference about it is IMO possibly because you're more likely to actually
not have upstream or downstream build at all.

Instead of having say a build, then a test, then a deploy build you have
only one pipeline, possibly leveraging the `parallel` step where needs be.

Cheers

Le 11 août 2016 8:45 AM, "'StuporMundi' via Jenkins Users" <
jenkinsci-users@googlegroups.com> a écrit :

> Hi everyone,
>
> I have a question regarding pipeline jobs in Jenkins 2.x. For freestyle
> jobs one always had the possibility to block their execution while one of
> their up and/or downstream dependencies were building (*Advanced Project
> Options --> Block build when upstream/downstream project is building*).
> For a pipeline or multi branch pipeline job these options are not
> available. Is there any other means by which I can achieve the effect those
> options had?
>
> To my surprise Google did not yield anything on that topic; I also tried stack
> overflow
> 
>  but
> my post went largely unnoticed. I would have thought that serializing
> dependent jobs would be a common requirement - or should I reconsider my
> build strategy?
>
> Anyway... Any input on that topic would be highly appreciated.
> Many thanks
>
> V
>
> --
> 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/66809c95-3f16-4671-88ba-676ffe361106%40googlegroups.
> com
> 
> .
> 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/CANWgJS6Ypbo_LgfzGqPdX8n0vW6b5Kentr0TrOyeS6C4tfRUZg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins Publish Over SSH for Jenkins Pipeline

2016-08-11 Thread Baptiste Mathus
You can simply use a plain ssh or scp call through an sh step, wrapped in
an sshagent step.

Cheers

Le 11 août 2016 8:31 AM, "ctime800"  a écrit :

> I need to use the Jenkins Publish over ssh plugin in the Jenkins
> pipeline.  What would be the syntax for this?  I tried to use the script
> generator but this one is not in the list.  Please advise.  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/ca946069-baed-4059-8ccb-60d15e84d239%40googlegroups.
> com
> 
> .
> 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/CANWgJS4PfqFv_ntkeU_kN%2B410tt-FJtfbemjgA80%3DiSaHB%2B1bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: New Pipeline Maven plugin

2016-08-11 Thread niristotle okram
Assuming maven was already installed in the node & have the files
configured (settings.xml, local repo etc) from the TOOLS setting of
jenkins..
Will this plugin override those settings?

 withMaven(mavenInstallation: 'M3', mavenLocalRepo: '.repository',
mavenSettingsConfig: 'maven-settings-for-gameoflife') {
// Run the maven buildsh "mvn clean install"
}



And is there any plan for the maven release plugin in pipeline? At the
moment i am using the 'bat' to call the goals for release:prepare and
release:perform



Thanks






On Thu, Aug 11, 2016 at 11:33 AM, Álvaro Lobato 
wrote:

>
> Hello everyone,
>
> I'd like to introduce you to the new Pipeline Maven
>  plugin .
> The intention of this plugin is to help using maven from pipeline, setting
> up a maven environment by using a withMaven step. This environment can
> later be called with sh or bat step.
>
> The supported configuration parameters are:
>
>- Maven Installation
>- JDK
>- Maven Settings Config (Config File Provider Plugin)
>- Maven Settings File Path
>- Maven JVM Opts
>- Maven Local Repository
>
> The step can be used used directly on a node or in a docker.inside.
>
> Currently it is in an early stage of development and I've just released
> the first beta version, already available in the update center.
>
> This is the start point for a more feature rich integration between
> pipeline and maven.
>
> You can find more information on the wiki page: Pipeline Maven plugin
> 
>
> Thanks
> Alvaro.
>
> --
> 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/81089a41-3bdf-47a4-bdad-b4424d27341b%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Regards
nirish okram

-- 
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/CAPzcO4g0yPF0rBYm89cY3N7gKvw3EYQwGX6W_%3D9K9bDBoBhcJQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: New Pipeline Maven plugin

2016-08-11 Thread Álvaro Lobato
Yes, thanks Daniel.

-- 
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/CAHBC%2BRu4%3D5ssQFvGWw_reJ2U-VBs_TXBJBJZojoq%2BweeFz2PQg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Automated Jenkins Plugin/Dependency Management

2016-08-11 Thread Slide
Kind of off topic, but it would really be nice to be able to "pin" a plugin
to a specific version that won't get upgraded.

On Thu, Aug 11, 2016 at 11:08 AM Daniel Beck  wrote:

>
> > On 11.08.2016, at 15:14, Jason Kulatunga  wrote:
> >
> > I'm not sure if anyone has done something similar but I wanted to get
> some feedback before I spent too much time investigating either idea.
>
> Note that pinning doesn't prevent a plugin from being upgraded -- it's
> related to Jenkins 1.x plugin bundling, and means that a plugin that's also
> bundled (e.g. subversion) won't get overwritten by the version bundled with
> Jenkins on startup. In Jenkins 2, it's basically irrelevant.
>
> --
> 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/3C393994-86E4-4048-9D99-2A4A258706BE%40beckweb.net
> .
> 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/CAPiUgVdCMKhe0ka_j1OMOU9XxkaXBVihJDhvjg207BgoQ%2BtBEQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: jenkins 2.7.2 sonarQube SonarQubeScanner not found

2016-08-11 Thread Daniel Beck
Manage Jenkins » Global Tool Configuration

> On 11.08.2016, at 12:06, Philippe Couas  wrote:
> 
> Hi,
> 
> I want install SonarQube with Jenkins2, but install screen not corresponding ?
> http://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner+for+Jenkins#AnalyzingwithSonarQubeScannerforJenkins-AddingSonarQubeServer
> 
> I don't found  SonarQubeScanner plugin in Jenkins2 ?
> 
> What is new method on Jenkins2 ?
> 
> Regards
> Phil
> 
> -- 
> 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/b9e9d748-4419-4f6c-b601-71a63d2c1d84%40googlegroups.com.
> 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/0A8BFBD1-1B58-4B30-9835-32E968B805BA%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.


Re: Automated Jenkins Plugin/Dependency Management

2016-08-11 Thread Daniel Beck

> On 11.08.2016, at 15:14, Jason Kulatunga  wrote:
> 
> I'm not sure if anyone has done something similar but I wanted to get some 
> feedback before I spent too much time investigating either idea. 

Note that pinning doesn't prevent a plugin from being upgraded -- it's related 
to Jenkins 1.x plugin bundling, and means that a plugin that's also bundled 
(e.g. subversion) won't get overwritten by the version bundled with Jenkins on 
startup. In Jenkins 2, it's basically irrelevant.

-- 
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/3C393994-86E4-4048-9D99-2A4A258706BE%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.


Re: Automated Jenkins Plugin/Dependency Management

2016-08-11 Thread Daniel Beck

> On 11.08.2016, at 15:14, Jason Kulatunga  wrote:
> 
> we've also verified that 'installNecessaryPlugins' does not actually respect 
> the version parameter. 

As the plugin update site metadata does not support arbitrary versions, it'll 
always install the one present in the JSON -- which is the latest compatible 
with your release.

This may work for you, but AFAIK still requires manual dependency resolution 
(we added it for UI uploads, but not for the CLI):

https://ci.jenkins.io/cli/command/install-plugin

-- 
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/262E4CEC-919A-49C2-ABDC-DB28849957BB%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.


Re: New Pipeline Maven plugin

2016-08-11 Thread Daniel Beck

> On 11.08.2016, at 18:33, Álvaro Lobato  wrote:
> 
> released the first beta version, already available in the update center

Experimental update site only:

https://jenkins.io/blog/2013/09/23/experimental-plugins-update-center/


-- 
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/D03DD471-2FEA-4D3C-B253-C08841CA5E94%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.


Re: Git Polling fails after upgrade

2016-08-11 Thread Mark Waite
The previous plugin version is usually stored in the plugins directory as
plugins/*.bak.  If you copy the plugins/*.[hj]pi file to a safe location,
you can then copy the .bak file over the existing hpi or jpi file.  The
next time jenkins starts, it will unpack that file and use it as the plugin.

Mark Waite

On Wed, Aug 10, 2016 at 5:34 PM Tecno Brain 
wrote:

> It also seems related to this
>  https://issues.jenkins-ci.org/browse/JENKINS-36249
> But without the UI, how do I change the plugin being used?
>
>
>
> On Wednesday, August 10, 2016 at 4:15:00 PM UTC-7, Tecno Brain wrote:
>
>> I am getting a similar problem:
>>
>> I get this error:
>> SEVERE: found cycle in plugin dependencies: (root=Plugin:git,
>> deactivating all involved) Plugin:git -> Plugin:workflow-scm-step ->
>> Plugin:git
>>
>> Followed by several exceptions.
>> How do I revert to the previous versions or upgrade to the right
>> plugin ?
>>
>> INFO: Injecting JRuby into XStream
>>
>> Trying to load models from
>> /var/lib/jenkins/plugins/rvm/WEB-INF/classes/models
>>
>> Loading /var/lib/jenkins/plugins/rvm/WEB-INF/classes/models/rvm_wrapper.rb
>>
>> Aug 10, 2016 10:40:26 PM jenkins.InitReactorRunner$1 onTaskFailed
>>
>> SEVERE: Failed Loading plugin managed-scripts
>>
>> java.io.IOException: Dependency config-file-provider (2.0) doesn't exist
>>
>> at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:523)
>>
>> at hudson.PluginManager$2$1$1.run(PluginManager.java:409)
>>
>> at
>> org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
>>
>> at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
>>
>> at jenkins.model.Jenkins$8.runTask(Jenkins.java:1009)
>>
>> at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
>>
>> at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>
>> at java.lang.Thread.run(Thread.java:745)
>>
>>
>> Aug 10, 2016 10:40:26 PM hudson.plugins.virtualbox.VirtualBoxPlugin start
>>
>> INFO: Starting VirtualBoxPlugin
>>
>> Aug 10, 2016 10:40:26 PM
>> jenkins.bouncycastle.api.SecurityProviderInitializer addSecurityProvider
>>
>> INFO: Initializing Bouncy Castle security provider.
>>
>> Aug 10, 2016 10:40:26 PM
>> jenkins.bouncycastle.api.SecurityProviderInitializer addSecurityProvider
>>
>> INFO: Bouncy Castle security provider initialized.
>>
>> Aug 10, 2016 10:40:26 PM
>> org.jvnet.hudson.plugins.m2release.M2ReleaseBuildWrapper$DescriptorImpl
>> 
>>
>> INFO: Using new style Permission with PermissionScope
>>
>> Trying to load models from
>> /var/lib/jenkins/plugins/chef/WEB-INF/classes/models
>>
>> Loading
>> /var/lib/jenkins/plugins/chef/WEB-INF/classes/models/chef-builder.rb
>>
>> Aug 10, 2016 10:40:33 PM hudson.ExtensionFinder$GuiceFinder$SezpozModule
>> configure
>>
>> WARNING: Failed to load
>> net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition$DescriptorImpl
>>
>> java.lang.NoClassDefFoundError: hudson/plugins/git/GitSCM
>>
>> at java.lang.Class.getDeclaredMethods0(Native Method)
>>
>> at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
>>
>> at java.lang.Class.privateGetPublicMethods(Class.java:2902)
>>
>> at java.lang.Class.getMethods(Class.java:1615)
>>
>> at
>> hudson.ExtensionFinder$GuiceFinder$SezpozModule.resolve(ExtensionFinder.java:480)
>>
>> at
>> hudson.ExtensionFinder$GuiceFinder$SezpozModule.configure(ExtensionFinder.java:509)
>>
>> at com.google.inject.AbstractModule.configure(AbstractModule.java:62)
>>
>> at
>> com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:230)
>>
>> at com.google.inject.spi.Elements.getElements(Elements.java:103)
>>
>> at
>> com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:136)
>>
>> at
>> com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104)
>>
>> at com.google.inject.Guice.createInjector(Guice.java:96)
>>
>> at com.google.inject.Guice.createInjector(Guice.java:73)
>>
>> at hudson.ExtensionFinder$GuiceFinder.(ExtensionFinder.java:280)
>>
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>>
>> at
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>>
>> at
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>>
>> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
>>
>> at java.lang.Class.newInstance(Class.java:442)
>>
>> at net.java.sezpoz.IndexItem.instance(IndexItem.java:181)
>>
>> at hudson.ExtensionFinder$Sezpoz._find(ExtensionFinder.java:637)
>>
>> at hudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:612)
>>
>> at
>> hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:482)
>>
>> at 

Re: Groovy code to access full path to a job, ie "Org/Project/branch" name

2016-08-11 Thread Greg Smith
Thanks!  That worked for exactly what I wanted.  

On Thursday, August 11, 2016 at 11:52:35 AM UTC-4, Cuong Tran wrote:
>
> Try getFullName()

-- 
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/21c1f278-dff7-4fc2-988f-857a552d641d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


New Pipeline Maven plugin

2016-08-11 Thread Álvaro Lobato

Hello everyone,

I'd like to introduce you to the new Pipeline Maven 
 plugin . 
The intention of this plugin is to help using maven from pipeline, setting 
up a maven environment by using a withMaven step. This environment can 
later be called with sh or bat step.

The supported configuration parameters are:

   - Maven Installation
   - JDK
   - Maven Settings Config (Config File Provider Plugin)
   - Maven Settings File Path 
   - Maven JVM Opts 
   - Maven Local Repository 

The step can be used used directly on a node or in a docker.inside.

Currently it is in an early stage of development and I've just released the 
first beta version, already available in the update center.

This is the start point for a more feature rich integration between 
pipeline and maven.

You can find more information on the wiki page: Pipeline Maven plugin 
 

Thanks
Alvaro.

-- 
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/81089a41-3bdf-47a4-bdad-b4424d27341b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Groovy code to access full path to a job, ie "Org/Project/branch" name

2016-08-11 Thread Cuong Tran
Try getFullName()

-- 
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/c824d19f-f3db-4b04-b99e-b333be3f28f0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Organizing artifacts?

2016-08-11 Thread Arnaud bourree
+1

2016-08-11 14:51 GMT+02:00 Jonathan Hodgson :

> Hi,
>
> I'm winding up with quite a lot of artifacts, logs, built code, test
> results etc.
>
> Is there a way that I could organize these so that it's not just a flat
> list on the build page?
>
> regards
>
> Jon
>
> --
> 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/1450a2e1-4824-4439-8207-352ac33805ce%40googlegroups.
> com
> 
> .
> 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/CAESUf_AD_NHZjW_nhNBGdKLPg6wbfu7gyC%3DBSZzGVLOnDZRo9w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: regarding jenkins CD in jenkins 2.0

2016-08-11 Thread Jesse McCormick
I wasn't really advocating running SQL scripts manually or via script 
runner, but if you have the requirement, it can be done. 

Since we are a java project, we use Flyway.

On Thursday, August 11, 2016 at 9:40:39 AM UTC-4, Zue Sani wrote:
>
> one more quick fire: I had a script for CD. for example if I had 5 
> successful builds... If I want to deploy build 4 , is the possible???  
>
> And could any let me know what is the best build and deployment scripts 
> for sql DB?? 
>
> On Wed, Aug 10, 2016 at 10:24 AM, suresh kumar  > wrote:
>
>> Hi Jesse McCormick,
>> Every time when deploying done manually updating the Jobs with sql 
>> scripts is not suggestible as this doesn't give full automation. As much as 
>> possible we have to eliminate manual tasks while achieving continuous 
>> deployment.
>>
>> -Suresh
>>
>>
>> On Wednesday, August 3, 2016 at 8:55:33 PM UTC+5:30, Jesse McCormick 
>> wrote:
>>>
>>> If you can script the SQL commands into a bash/batch script, then you 
>>> should still be able to execute them. If you are using Oracle, there is 
>>> also this plugin: 
>>> https://wiki.jenkins-ci.org/display/JENKINS/SQLPlus+Script+Runner+Plugin
>>>
>>>
>>> On Wednesday, August 3, 2016 at 10:28:26 AM UTC-4, Zue Sani wrote:

 Can we run sql scripts to deploy, which we have been using for manual 
 running of scripts

 On Sat, Jul 30, 2016 at 10:10 PM, suresh kumar  
 wrote:

> Hi Zue Sani,
> There are lot of Open Source and Commercial tools which provides 
> options for migrating database sql scripts.
> Each having their own process to prepare scripts.
> Some of OpenSource tools and also having Jenkins plugins to migrate 
> scripts.
> 1) Liquibase
> 2) Flyway
>
> Have a look at these official documentation and usage of Jenkins of 
> their respective plugins.
>
> -Suresh
>
> On Saturday, July 30, 2016 at 7:44:46 PM UTC+5:30, Zue Sani wrote:
>>
>> hi,
>>
>> I had few questions on CD:
>>
>>
>> 1.) we are performing deployments manually using sql scripts. Can the 
>> same scripts run on jenkins when we automate the deployment?.  (I heard 
>> we 
>> need to change them to dacpac scripts is that true?)
>>
>>
>> -- 
> You received this message because you are subscribed to a topic in the 
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-users/JxJ-uIO-AD8/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/36caa94b-539f-4880-a093-5519b0d9b601%40googlegroups.com
>  
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

 -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Jenkins Users" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/jenkinsci-users/JxJ-uIO-AD8/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/25cc034e-da2a-4ad8-9e58-825750859d1a%40googlegroups.com
>>  
>> 
>> .
>>
>> 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/9141b630-ca15-4531-99de-15239b445500%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Pipeline script for Build Trigger

2016-08-11 Thread Michal Medvecky
I see that the related issue was resolved, but I still don't know how to 
add "Build when a change is pushed to GitHub" support to my Jenkinsfile.

Can anyone help me please?

Michal

-- 
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/5b768994-af7f-48dc-90d7-ff046fe1febb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: regarding jenkins CD in jenkins 2.0

2016-08-11 Thread Zue Sani
one more quick fire: I had a script for CD. for example if I had 5
successful builds... If I want to deploy build 4 , is the possible???

And could any let me know what is the best build and deployment scripts for
sql DB??

On Wed, Aug 10, 2016 at 10:24 AM, suresh kumar  wrote:

> Hi Jesse McCormick,
> Every time when deploying done manually updating the Jobs with sql scripts
> is not suggestible as this doesn't give full automation. As much as
> possible we have to eliminate manual tasks while achieving continuous
> deployment.
>
> -Suresh
>
>
> On Wednesday, August 3, 2016 at 8:55:33 PM UTC+5:30, Jesse McCormick wrote:
>>
>> If you can script the SQL commands into a bash/batch script, then you
>> should still be able to execute them. If you are using Oracle, there is
>> also this plugin: https://wiki.jenkins-ci.org/di
>> splay/JENKINS/SQLPlus+Script+Runner+Plugin
>>
>>
>> On Wednesday, August 3, 2016 at 10:28:26 AM UTC-4, Zue Sani wrote:
>>>
>>> Can we run sql scripts to deploy, which we have been using for manual
>>> running of scripts
>>>
>>> On Sat, Jul 30, 2016 at 10:10 PM, suresh kumar 
>>> wrote:
>>>
 Hi Zue Sani,
 There are lot of Open Source and Commercial tools which provides
 options for migrating database sql scripts.
 Each having their own process to prepare scripts.
 Some of OpenSource tools and also having Jenkins plugins to migrate
 scripts.
 1) Liquibase
 2) Flyway

 Have a look at these official documentation and usage of Jenkins of
 their respective plugins.

 -Suresh

 On Saturday, July 30, 2016 at 7:44:46 PM UTC+5:30, Zue Sani wrote:
>
> hi,
>
> I had few questions on CD:
>
>
> 1.) we are performing deployments manually using sql scripts. Can the
> same scripts run on jenkins when we automate the deployment?.  (I heard we
> need to change them to dacpac scripts is that true?)
>
>
> --
 You received this message because you are subscribed to a topic in the
 Google Groups "Jenkins Users" group.
 To unsubscribe from this topic, visit https://groups.google.com/d/to
 pic/jenkinsci-users/JxJ-uIO-AD8/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 jenkinsci-use...@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/ms
 gid/jenkinsci-users/36caa94b-539f-4880-a093-5519b0d9b601%
 40googlegroups.com
 
 .

 For more options, visit https://groups.google.com/d/optout.

>>>
>>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-users/JxJ-uIO-AD8/unsubscribe.
> To unsubscribe from this group and all its topics, 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/25cc034e-da2a-4ad8-9e58-825750859d1a%40googlegroups.
> com
> 
> .
>
> 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/CAKMcRdA%3D_wVJ8R_OgjKrjkUbCLy8WvyiOBysip%3DO2qcYMi023A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Organizing artifacts?

2016-08-11 Thread Jonathan Hodgson
Hi,

I'm winding up with quite a lot of artifacts, logs, built code, test 
results etc.

Is there a way that I could organize these so that it's not just a flat 
list on the build page?

regards

Jon

-- 
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/1450a2e1-4824-4439-8207-352ac33805ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: CAS plugin with Jenkins 2

2016-08-11 Thread cma
Never mind. I messed up with the Apache reverse proxy, which terminates my 
TLS. All redirects from the CAS plugin to the CAS server were re-written by 
Apache http to point back to itself.

In any case, thanks for confirming that the setup Jenkins 2.17 and CAS 2.0 
should work!

~Chris

Am Mittwoch, 10. August 2016 17:15:48 UTC+2 schrieb 
matthew...@diamond.ac.uk:
>
> I use the CAS plugin v1.2.0 using CAS protocol 2.0, and Jenkins 2.17.
>
> We have not had any CAS-related issues (never, I think).
>
> However, we run our Jenkins on http (not https), using the embedded web 
> server (Jetty?), and not in a container like Tomcat.
>
>  
>
> Did you have this working, and then it broke, or are you trying to set it 
> up for the first time?
>
>  
>
> Matthew
>
> *From:* jenkins...@googlegroups.com  [mailto:
> jenkins...@googlegroups.com ] *On Behalf Of *c...@nine.ch 
> 
> *Sent:* 10 August 2016 15:44
> *To:* Jenkins Users
> *Subject:* CAS plugin with Jenkins 2
>
>  
>
> I'm having troubles with the CAS plugin.
>
>  
>
> The plugin will redirect me to my CAS server. When I authenticate on the 
> CAS server, I get redirected to jenkins.
>
> Now I should be logged in, but I'm not.
>
>  
>
> I get redirected to 
> https://jenkins01/login?service=https%3A%2F%2Fjenkins01%2FsecurityRealm%2FfinishLogin
>
> ... which seems like Jenkins protects the finishLogin page.
>
>  
>
> Does anyone has the CAS plugin (CAS 2.0 protocol) working with Jenkins 
> >2.9? (I tested with 2.9 and 2.17)
>
>  
>
> Plus it would be helpful if someone could guide me to what Loggers on 
> which Levels I should listen to. Now I either get noise or nothing.
>
>  
>
> ~Chris
>
> -- 
>
>  
>
> -- 
>
> This e-mail and any attachments may contain confidential, copyright and or 
> privileged material, and are for the use of the intended addressee only. If 
> you are not the intended addressee or an authorised recipient of the 
> addressee please notify us of receipt by returning the e-mail and do not 
> use, copy, retain, distribute or disclose the information in or attached to 
> the e-mail.
> Any opinions expressed within this e-mail are those of the individual and 
> not necessarily of Diamond Light Source Ltd. 
> Diamond Light Source Ltd. cannot guarantee that this e-mail or any 
> attachments are free from viruses and we cannot accept liability for any 
> damage which you may sustain as a result of software viruses which may be 
> transmitted in or with the message.
> Diamond Light Source Limited (company no. 4375679). Registered in England 
> and Wales with its registered office at Diamond House, Harwell Science and 
> Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
>  
>

-- 
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/832aa5d2-2ab0-47c2-8763-d1ca9f705887%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


jenkins 2.7.2 sonarQube SonarQubeScanner not found

2016-08-11 Thread Philippe Couas
Hi,

I want install SonarQube with Jenkins2, but install screen not 
corresponding ?
http://docs.sonarqube.org/display/SCAN/Analyzing+with+SonarQube+Scanner+for+Jenkins#AnalyzingwithSonarQubeScannerforJenkins-AddingSonarQubeServer

I don't found  SonarQubeScanner plugin in Jenkins2 ?

What is new method on Jenkins2 ?

Regards
Phil

-- 
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/b9e9d748-4419-4f6c-b601-71a63d2c1d84%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Error on Windows Slaves

2016-08-11 Thread mosh5cis
Can you check if you have write permissions under 
e:\jenkins\workspace\Jobfolder 
folder?

Also can you share the full log?

On Thursday, 11 August 2016 04:17:17 UTC+5:30, Sajith Majeed - Saaj wrote:
>
> We started receiving the below error from yesterday on our windows slaves. 
> This was working until yesterday and started to happen all of a sudden. 
> Have anyone seen this error and help us with some inputs on this?
>
>
> java.io.IOException: remote file operation failed: 
> e:\jenkins\workspace\Jobfolder
>  at hudson.remoting.Channel@3c3e8ed5:WINDOWSHOST: java.io.IOException: The 
> filename, directory name, or volume label syntax is incorrect
>
>
>
>
> Thanks | Sajith
>
>

-- 
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/f4b639bd-ffa8-49d4-869a-247bc6bbb71b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Blocking Pipeline builds while Up- and Downstream Dependencies are building

2016-08-11 Thread 'StuporMundi' via Jenkins Users
Hi everyone,

I have a question regarding pipeline jobs in Jenkins 2.x. For freestyle 
jobs one always had the possibility to block their execution while one of 
their up and/or downstream dependencies were building (*Advanced Project 
Options --> Block build when upstream/downstream project is building*). For 
a pipeline or multi branch pipeline job these options are not available. Is 
there any other means by which I can achieve the effect those options had?

To my surprise Google did not yield anything on that topic; I also tried stack 
overflow 

 but 
my post went largely unnoticed. I would have thought that serializing 
dependent jobs would be a common requirement - or should I reconsider my 
build strategy?

Anyway... Any input on that topic would be highly appreciated.
Many thanks

V

-- 
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/66809c95-3f16-4671-88ba-676ffe361106%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Jenkins Publish Over SSH for Jenkins Pipeline

2016-08-11 Thread ctime800
I need to use the Jenkins Publish over ssh plugin in the Jenkins pipeline. 
 What would be the syntax for this?  I tried to use the script generator 
but this one is not in the list.  Please advise.  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/ca946069-baed-4059-8ccb-60d15e84d239%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Jenkins Pipeline Groovy Script and JSON

2016-08-11 Thread Łukasz Zachulski
Please check SO thread for details regarding JSON file parsing in Jenkinsfile, 
http://stackoverflow.com/q/37864542/6128602. 

-- 
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/e72c098e-160f-42c5-85aa-fafa4c3ddfb2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.