Re: What is best way to upgrade jenkins from 2.235.2 to latest .

2023-05-12 Thread Adrien Lecharpentier
Glad I could help.

I know it can be difficult, but don't postpone upgrades too much because
you're missing security fixes, bug fixes, general improvements and
generally, big upgrade like you had to do are more painful than small steps
upgrade.

Le ven. 12 mai 2023, 10:59, Ravindra Verma  a
écrit :

> Thanks Adrien ,
>
> It worked smoothly , upgraded to LTS without any problems .
>
>
>
> On Thu, May 11, 2023 at 3:02 PM Adrien Lecharpentier <
> adrien.lecharpent...@gmail.com> wrote:
>
>> Hello,
>>
>> Since 2.361.x, Jenkins requires a JVM 11 to run. Would it be by any
>> chance the reason why it failed in your previous attempts?
>>
>> I would suggest you to first, backup your installation.
>> Then, upgrade to 2.346.3, upgrade the plugins. Validates that all works,
>> take a new backup. Then upgrade the JVM used. Take a second backup of the
>> installation.
>> Then, upgrade to 2.361.4 and the required plugins.
>> Take a new backup.
>>
>> At this point, you can upgrade to the latest lts version.
>>
>> Backups will help you in case an upgrade of a plugin had to change the
>> data structure store in your Jenkins Home.
>>
>> Hoping this helps.
>>
>> Le jeu. 11 mai 2023, 10:23, Ravindra Verma 
>> a écrit :
>>
>>> Hi Folks ,
>>>
>>> I have Jenkins 2.235.2 installed on ubuntu machine using package manger
>>> , it has many vulnerable  plugging as well .
>>>
>>> I tried to upgrade it latest version using upgrade guide with the
>>> package manger but had 3 failure attempts with many bootstrap error and had
>>> to roll back with snapshot .
>>>
>>> Please suggest me what is best way to prepare it for upgrade without
>>> failure .
>>>
>>>
>>> --
>>> 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/6263fce8-f574-42bc-81aa-8333a6761282n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/6263fce8-f574-42bc-81aa-8333a6761282n%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 jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/CAKwJSvyto-ZdtAxE4KnkpFTvuMy5yxiVG%2BsmZyevMBO1igAjgw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/CAKwJSvyto-ZdtAxE4KnkpFTvuMy5yxiVG%2BsmZyevMBO1igAjgw%40mail.gmail.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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAOnDU%3D40FVi%2BDmp63XD-p45cpg03tDssTTz1NSDA_XoOcYV3_A%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAOnDU%3D40FVi%2BDmp63XD-p45cpg03tDssTTz1NSDA_XoOcYV3_A%40mail.gmail.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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAKwJSvxBJFLB9p7Jxm3uoUNFdcWVeonyDtZKcYKaqpjdUZRzhg%40mail.gmail.com.


Re: What is best way to upgrade jenkins from 2.235.2 to latest .

2023-05-11 Thread Adrien Lecharpentier
Hello,

Since 2.361.x, Jenkins requires a JVM 11 to run. Would it be by any chance
the reason why it failed in your previous attempts?

I would suggest you to first, backup your installation.
Then, upgrade to 2.346.3, upgrade the plugins. Validates that all works,
take a new backup. Then upgrade the JVM used. Take a second backup of the
installation.
Then, upgrade to 2.361.4 and the required plugins.
Take a new backup.

At this point, you can upgrade to the latest lts version.

Backups will help you in case an upgrade of a plugin had to change the data
structure store in your Jenkins Home.

Hoping this helps.

Le jeu. 11 mai 2023, 10:23, Ravindra Verma  a
écrit :

> Hi Folks ,
>
> I have Jenkins 2.235.2 installed on ubuntu machine using package manger ,
> it has many vulnerable  plugging as well .
>
> I tried to upgrade it latest version using upgrade guide with the package
> manger but had 3 failure attempts with many bootstrap error and had to roll
> back with snapshot .
>
> Please suggest me what is best way to prepare it for upgrade without
> failure .
>
>
> --
> 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/6263fce8-f574-42bc-81aa-8333a6761282n%40googlegroups.com
> 
> .
>

-- 
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/CAKwJSvyto-ZdtAxE4KnkpFTvuMy5yxiVG%2BsmZyevMBO1igAjgw%40mail.gmail.com.


Re: Artifact deployer error failed to deploy

2021-11-05 Thread Adrien Lecharpentier
Hello,

I think it would be great if you could create a ticket on issues.jenkins.io.
Please provide: jenkins version, plugin version, jdk version, context (job,
external tools you try to deploy to). A great thing would be to have a
support bundle, generated by the support-core plugin attached to the
ticket, as it would provide most of the details.

In the end,
> Java.io.Exception remote call on host failed
is not enough. We don't know enough about the context of the stack trace
(which class throw it for instance) to understand why you have this
problem.
Many thing can happen: your Jenkins instance has no connection to the
target, which is likely the case, a bug in the code of the plugin, etc.

So, are you sure the deployment target is reachable from your jenkins
instance? Could you add a shell script (or cmd) to ping the deployment
target before trying to use the artifact deployer plugin? Was the
configuration working before or is it a new configuration that you run for
the first time? If it worked before, what changed (upgrades? environment
modifications?, etc)?

Thanks.


Le ven. 5 nov. 2021 à 10:21, Adharsha sri  a
écrit :

> Can you please let me know what are the details need to be added.
>
> On Fri, 5 Nov 2021, 2:38 pm 'Dirk Heinrichs' via Jenkins Users, <
> jenkinsci-users@googlegroups.com> wrote:
>
>> Am Freitag, dem 05.11.2021 um 14:28 +0530 schrieb Adharsha sri:
>>
>> We are using artifact deployer plugin but getting the below error
>> Failed to deploy . Java.io.Exception remote call on host failed. Please
>> help to resolve this issue.
>>
>>
>> Please do not, under any circumstance, provide more details. Someone
>> might be able to help you... *SCNR*
>>
>> Bye...
>>
>> Dirk
>>
>> --
>>
>> *Dirk Heinrichs*
>> Senior Systems Engineer, Delivery Pipeline
>> OpenText ™ Discovery | Recommind
>> *Phone*: +49 2226 15966 18
>> *Email*: dhein...@opentext.com
>> *Website*: www.recommind.de
>> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
>> Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan,
>> Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
>> This e-mail may contain confidential and/or privileged information. If
>> you are not the intended recipient (or have received this e-mail in error)
>> please notify the sender immediately and destroy this e-mail. Any
>> unauthorized copying, disclosure or distribution of the material in this
>> e-mail is strictly forbidden
>> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
>> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
>> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
>> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
>> Weitergabe dieser Mail sind nicht gestattet.
>>
>> --
>> 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/f706e2761caedc269f998ba6318716f32007bd43.camel%40opentext.com
>> 
>> .
>>
> --
> 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/CAJWGB6qoaY2TnXt1__gG%2Bb-ho6LyuqYUxCV2Rui-Vpgxrrx4_Q%40mail.gmail.com
> 
> .
>

-- 
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/CAKwJSvz%2By8d5RdE1AVo_guwGd6BzXX_42v1Wr-sPq7TBDf-aiQ%40mail.gmail.com.


Re: How to stash file in free style job

2020-09-04 Thread Adrien Lecharpentier
Hello,

You need to archive the XML file in the first project and then use
cooyartifact plugin in the downstream job to get that file..

The plugin documentation will help you set it up.

-- Adrien

Le ven. 4 sept. 2020 à 17:32, 02.m...@gmail.com <02.mah...@gmail.com> a
écrit :

> I have a free style job that generates a XML file and now I want to use
> that file in a downstream project. I can create a downstream project but
> how do get the XML file from upstream project?
>
> Any help appreciated.
>
> --
> 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/c40d2701-1d1f-4721-98a2-3454721d7b47n%40googlegroups.com
> 
> .
>

-- 
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/CAKwJSvwZOA4SXC51%3DJQ%3DLwztpHqnRwFZ8VpMf9_rSgHyBDsonQ%40mail.gmail.com.


Re: how to hidden or custom the error page (stack trace), thanks

2020-01-22 Thread Adrien Lecharpentier
If you used the Suppress Stack Trace plugin but you still have the stack
traces, maybe you need to fill a bug on the plugin tracker.

Le mer. 22 janv. 2020 à 15:53, Momo  a écrit :

>
> Jenkins was vulnerability detected by web vulnerability scanner
> when entering a specific string on the login page, it causes Jenkins to
> generate error message as follow...
> how to disable(hidden) or custom error page to solve this vulnerability
> (sensitive information)...
>
> i tried
> 1. use the latest version (Jenkins)
> 2. edit web.xml ()
> 3. use suppress stack trace plugin
> but still show Oops! and stack trace message
>
> Thanks!
>
> Stack trace
> org.eclipse.jetty.util.Utf8Appendable$NotUtf8Exception: Not valid UTF8!
> byte Bf in state 0
> at
> org.eclipse.jetty.util.Utf8Appendable.appendByte(Utf8Appendable.java:254)
> at
> org.eclipse.jetty.util.Utf8Appendable.append(Utf8Appendable.java:155)
> at org.eclipse.jetty.util.UrlEncoded.decodeUtf8To(UrlEncoded.java:522)
> at org.eclipse.jetty.util.UrlEncoded.decodeTo(UrlEncoded.java:577)
> at
> org.eclipse.jetty.server.Request.extractFormParameters(Request.java:568)
> at
> org.eclipse.jetty.server.Request.extractContentParameters(Request.java:519)
> at org.eclipse.jetty.server.Request.getParameters(Request.java:430)
> Caused: org.eclipse.jetty.http.BadMessageException: 400: Unable to parse
> form content
> at org.eclipse.jetty.server.Request.getParameters(Request.java:434)
> at org.eclipse.jetty.server.Request.getParameter(Request.java:1059)
> at
> org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.obtainUsername(AuthenticationProcessingFilter.java:113)
> at
> org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:53)
> at
> org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252)
> at
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
> at
> jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93)
> .
>
> --
> 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/c3aee488-f1be-403c-9f95-96654d2e2fca%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/c3aee488-f1be-403c-9f95-96654d2e2fca%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Adrien Lecharpentier

-- 
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/CAKwJSvyDWXa4hUPQF9r-Tzr8h%3DmpjLjO-pMbjY8LB33vyThWEw%40mail.gmail.com.


Re: About SMTPSendFailedException

2019-09-25 Thread Adrien Lecharpentier
Hello,

I'm wondering which version of the Mailer plugin you are using on your
instance.
Is it possible that you are using a version between 1.25 and 1.27 (both
included)?
If so, please upgrade to 1.28 because you might be facing
https://issues.jenkins-ci.org/browse/JENKINS-59430.

BR,
-- Adrien

Le mer. 25 sept. 2019 à 09:25, Ajij Shaikh  a écrit :

> Hey,
>
> I am trying Jenkins for email notification please check below
> configuration and suggest the solution for it -
>
> 1. under manage Jenkins -> configure system I have set the configuration
> PFB screenshot -
>
> 2. On the same page when I check below box and give email id there to test
> connection then it sends mail successfully
>
> Test configuration by sending a test e-mail
>
> But this fails when we create the job and add mail id to post build
> actions -> Email notification -> recipient
> and check the box PFA screenshot for that
> Send e-mail for every unstable build and Send separate e-mails to
> individuals who broke the build
>
>
> 3. and trigger to a failed build
>
> 4. Unable to send the email see the stack trace of the build ---
>
>
> Started by user ajij <http://localhost:/user/admin>
> Running as SYSTEM
> Building in workspace /var/lib/jenkins/workspace/test1
> [test1] $ /bin/sh -xe /tmp/jenkins2681186595655127592.sh
> + [ -f  ]
> + echo  not found.
>  not found.
> + exit 1
> Build step 'Execute shell' marked build as failure
> Sending e-mails to: ajijsha...@gofynd.com
> ERROR: 530-5.5.1 Authentication Required. Learn more at
> 530 5.5.1  https://support.google.com/mail/?p=WantAuthError 
> m68sm4994696pfb.122 - gsmtp
>
> com.sun.mail.smtp.SMTPSendFailedException: 530-5.5.1 Authentication Required. 
> Learn more at
> 530 5.5.1  https://support.google.com/mail/?p=WantAuthError 
> m68sm4994696pfb.122 - gsmtp
>
>   at 
> com.sun.mail.smtp.SMTPTransport.issueSendCommand(SMTPTransport.java:2057)
>   at com.sun.mail.smtp.SMTPTransport.mailFrom(SMTPTransport.java:1580)
>   at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1097)
>   at javax.mail.Transport.send0(Transport.java:195)
>   at javax.mail.Transport.send(Transport.java:124)
>   at hudson.tasks.MailSender.run(MailSender.java:130)
>   at hudson.tasks.Mailer.perform(Mailer.java:175)
>   at hudson.tasks.Mailer.perform(Mailer.java:138)
>   at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)
>   at hudson.model.Build$BuildExecution.post2(Build.java:186)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)
>   at hudson.model.Run.execute(Run.java:1843)
>   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
>   at hudson.model.ResourceController.execute(ResourceController.java:97)
>   at hudson.model.Executor.run(Executor.java:429)
>
> Finished: FAILURE
>
>
> Quick help is appreciated
>
>
>
>
> --
> 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/b114ca5a-3251-4999-bbd4-7cc506c0941d%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/b114ca5a-3251-4999-bbd4-7cc506c0941d%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>


-- 
Adrien Lecharpentier

-- 
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/CAKwJSvwneZdD-jSK_r9io81DFRAb1Zaqv_aEcBRPfnMp2%3DddwA%40mail.gmail.com.


Re: Trying to compile docker-plugin -- failure "java: cannot find symbol Messages"

2019-03-26 Thread Adrien Lecharpentier
I'm wondering how are you trying to compile it? From CLI with `mvn compile`
or from your IDE?

>From the IDE, you would need to add to classpath the folder
`target/generated-sources/localise` (not sure about the last folder, but
you should have only two folders in this path).

If there is nothing there, run `mvn generate-sources` first.

The class missing are generated from the `Messages.properties` files and
are the localisation messages, generally for the UI.

-- Adrien

Le mar. 26 mars 2019 à 00:52, Richard Landon  a
écrit :

> I see the following 3 error messages trying to compile the Docker plugin
> from sources on github.
>
> git repo: https://github.com/jenkinsci/docker-plugin.git (branch is
> master).
> Envronment Idea; MacOS Mojave; JDK 8 (8.0.202-zulu); followed plugin
> development getting started et al:
> https://wiki.jenkins.io/display/JENKINS/Plugin+tutorial#Plugintutorial-SettingupaproductiveenvironmentwithyourIDE
>
> Here are the message failures.
> Any help appreciated.
>
> Error:(183, 37) java: cannot find symbol
>   symbol:   variable Messages
>   location: class
> com.nirima.jenkins.plugins.docker.DockerDisabled.DescriptorImpl
>
> Error:(42, 16) java: cannot find symbol
>   symbol:   variable Messages
>   location: class com.nirima.jenkins.plugins.docker.DockerManagement
>
> Error:(47, 16) java: cannot find symbol
>   symbol:   variable Messages
>   location: class com.nirima.jenkins.plugins.docker.DockerManagement
>
> --
> 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/634d2308-5664-4306-a407-a84f3f8bf07b%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/CAKwJSvz8g9ERbFPrBMrrnxHTo4q5zdLveKq4GWOc5muy3z2%3DjQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Multiple `archiveArtifacts` commands in one Jenkins pipeline

2019-02-15 Thread Adrien Lecharpentier
as a workaround, you could try to `stash` the binaries and `unstash` them
all in the same node and archive them then.

But for your problem, it's the first time I see this. Sorry.

Le ven. 15 févr. 2019 à 14:01, László Boros  a
écrit :

> Anyone with a similar issue? I'd really appreciate any tip.
>
> Thanks!
> Laci
>
> > On 13 Feb 2019, at 10:37, László Boros 
> wrote:
> >
> > Hi everyone!
> >
> > We are facing some issues with our main Jenkins pipeline. It consists of
> multiple stages which are executed on different machines, and each stage
> can produce artifacts. We are trying to archive these all by calling the
> `archiveArtifacts` pipeline command after each stage, but it seems these
> calls are not playing well together, since each time it runs the previous
> artifacts (from the previous stage) are removed and as a consequence only
> the last stage has its artifacts archived, no matter which stage it is.
> > Is there a way to merge the results and disable the directory clearing
> when calling `archiveArtifacts`? We tried to use the deprecated
> `latestOnly` boolean parameter as well, but it did not work.
> >
> > Thanks in advance!
> > Laci
>
> --
> 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/F826533E-4B3A-40D5-9FC9-494D9BE4293F%40skyscanner.net
> <https://groups.google.com/d/msgid/jenkinsci-users/F826533E-4B3A-40D5-9FC9-494D9BE4293F%40skyscanner.net?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Adrien Lecharpentier

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


Re: Try to use Jenkins first time.. It wipe my entire project source code.

2019-02-07 Thread Adrien Lecharpentier
Hello,

I'm afraid there is no solution.

When you changed the workspace of the job, you stated that Jenkins should
use the code you had in a specific folder. Then you asked Jenkins to remove
anything from the workspace before doing anything.

Basically, you asking Jenkins to `cd MY_PRECIOUS_CODE_FOLDER && rm -rf *`.

The "wipe out current workspace" can be handy when you get the source code
from a SCM (Git, Subversion, Mercurial, etc.). It seems it is not the case
here.

May I suggest something for next time:
 - don't change the default workspace, use a SCM
 - you can use Git to have a repository of code with your project and use
Jenkins to clone this repository (yes, even a local one) with a URI like
`file:///tmp/my-precious-code`

Le jeu. 7 févr. 2019 à 14:06, Smith Lo  a écrit :

> Of course I should have some backup. but I do not expect Jenkins can wipe
> the source code. My bad.
>
> The story is;
> - I try to study testing automation which instructor introduce TestNG,
> Maven and then Jenkins.
> - I create a simple project in Intellij with Maven and try to be able to
> execute testing separate by XML file by using testNG profile
> - then install Jenkins and use custom workspace to link with project in my
> local machine. I have to 'move' the project source code under /Jenkins
> folder
> - Then, I start job and I want to delete that job and I see only "Wipe
> Out Current Workspace <http://localhost:8080/job/MavenJob/ws/#>". I
> realize it later that I should use a hidden 'delete build' instead.
>
> I try to goggle but can't find any topic talking about recover Wipe Out
> Current Workspace.
>
> ;_;
>
> May I ask you guys are there anything that important for a Jenkins newbie
> should aware of?
>
> Thanks
> Smith
>
> --
> 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/31b56462-3feb-4175-9e09-7a144b42b646%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/31b56462-3feb-4175-9e09-7a144b42b646%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Adrien Lecharpentier

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


Re: Jenkins Plugin upgrade from 1.454 to 1.651.3

2019-02-06 Thread Adrien Lecharpentier
If I recall correctly, since `plugin-pom` 2.0, the version of the Jenkins
the plugin is built for is set with the `jenkins.version` property, as
Victor said. So you could basically use the latest `plugin-pom` (3.37) and
stil compile for `1.651.3`.
It's a minimal core version requirement. Doesn't mean that it won't work on
older versions nor it will work either on newer versions.
-- Adrien

Le mer. 6 févr. 2019 à 11:06, Victor Martinez 
a écrit :

> IIUC, you would like to use a WAR file different than the default one, if
> so, then you might need to use the properties section to enforce the
> version you'd like to:
>
> - https://github.com/jenkinsci/plugin-pom/tree/plugin-2.0
>
> ...
>  
>
> org.jenkins-ci.plugins
> plugin-pom
> 2.0
> 
>
> 
> 1.651.3
>
> 
>
>
>
> I have not tried though, but something like that it should work I guess
> so. Other than that, if you got some specific questions about plugin
> developoment it's worth to ask to the Jenkins Developers mailing
> list jenkinsci-dev
>
> Cheers
>
> --
> 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/c4f4ed52-8ca4-4e5e-b0c0-2e44f3ad6681%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/c4f4ed52-8ca4-4e5e-b0c0-2e44f3ad6681%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Adrien Lecharpentier

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


Re: Creating 2 pipelines in a single jenkinsfile

2019-01-10 Thread Adrien Lecharpentier
I agree with Arnaud.

However, having an input means that if you cancel the input, you'll have
aborted the build. So, even if the first 3 steps are successful, you'll
have an aborted build.

You could try/catch the input, but that will complexify the pipeline imo.

Could you explain why you need to conditionally upload the results and not
doing it each time it's successful? If you have some concerns about the
"space usage", you could make sure to replace the same package each time,
or configure nexus to have some cleanup tasks.

Le jeu. 10 janv. 2019 à 19:49, Arnaud bourree  a
écrit :

> Hi,
>
> Denis answer is good but why are you doing that?
> You said if pipeline #1 succeed, you run pipeline #2 which redo same steps
> including git checkout then push result to nexus.
> But you don't have guarantee that git checkout will fetch same source
> code.
> Why not add input validation on nexus stage in single pipeline?
>
> Arnaud
>
> Le jeu. 10 janv. 2019 à 17:54, Denis  a écrit :
>
>> You can create two pipeline jobs and have the first one trigger the
>> second one as a downstream job.
>> i.e in a finally block you can check the result of the build and trigger
>> the pipeline that publish to nexus
>>
>> On January 10, 2019 5:30:03 PM GMT+02:00, Faad Sayaou 
>> wrote:
>>>
>>> I was thinking maybe doing something like this would help but
>>> unfortunately not
>>>
>>> node {
>>> stages
>>>
>>> }
>>>
>>> node2 {
>>>
>>> stages
>>>
>>> }
>>>
>>>
>>> but it is viewed by jenkins as a single pipeline. I am using the
>>> scripted pipeline syntax
>>>
>>> On Thursday, 10 January 2019 16:25:11 UTC+1, Faad Sayaou wrote:
>>>>
>>>> Hi everyone,
>>>> I have this scenario i would like to implement but i don not know if
>>>> that is possible within a single jenkinsfile.
>>>> My idea was to have 2 pipelines
>>>>
>>>> 1st pipeline
>>>>  -git checkout
>>>>  -build
>>>>  -Test
>>>>
>>>> 2nd pipeline
>>>>
>>>> if first build from the first pipeline was successful, then
>>>>
>>>> -re-do the first 3 stages from 1st pipeline
>>>> -zip the build results
>>>> -and push to nexus
>>>>
>>>> ..is this however feasible within a single jenkinsfile?
>>>>
>>>> thanks
>>>>
>>>>
>> --
>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>>
>> --
>> 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/97F68F8F-DB51-4C09-B894-D8A57A30DFB0%40gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/97F68F8F-DB51-4C09-B894-D8A57A30DFB0%40gmail.com?utm_medium=email&utm_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/CAESUf_AYVtmQN%2BhinWSB-DgLtZ3QKTHYn0woYeEHQLfEwiBw4Q%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAESUf_AYVtmQN%2BhinWSB-DgLtZ3QKTHYn0woYeEHQLfEwiBw4Q%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Adrien Lecharpentier

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


Re: docker image for jenkins:lts is not latest

2018-12-10 Thread Adrien Lecharpentier
The docker image `jenkins` is deprecated for a longtime. The ofificial
image you need to pull and use is, as you guest, `jenkins/jenkins`. The
`jenkins` image will soon no longer be published / updated.

Le lun. 10 déc. 2018 à 02:44, RAJENDRA PRASAD 
a écrit :

> Jenkins can be downloaded from here:
> https://jenkins.io/download/
>
> Latest stable or LTS build is: 2.150.1
>
> Weekly release: 2.154 (this is not throughly tested).
>
> Thanks,
> Rajendra
>
> On Fri, 7 Dec, 2018, 13:08 Dan Tran 
>> Hi
>>
>> Current docker image for  jenkins:lts is not latest - 2.150.1
>>
>> Could someone confirm?  otherwise, it  may be something to do with my env
>>
>> Thanks
>>
>> -D
>>
>>
>>
>>
>> --
>> 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/262a206d-3bee-457d-85a4-12eefd9ede92%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/262a206d-3bee-457d-85a4-12eefd9ede92%40googlegroups.com?utm_medium=email&utm_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/CAMrg02TfoVOfD0XjFA5XPpQNEOP%2BqD21gy5P6dRS%2Bg%2Bq8O6mMA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAMrg02TfoVOfD0XjFA5XPpQNEOP%2BqD21gy5P6dRS%2Bg%2Bq8O6mMA%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Adrien Lecharpentier

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


Re: Changing Jenkins URL

2018-10-24 Thread Adrien Lecharpentier
This is a more global setup configuration. I'm not sure this can be
answered on this mailing list.

It's not different from setting up a DNS entry for a website.

Le mar. 23 oct. 2018 à 23:35, Faad Sayaou  a écrit :

> Hi thanks for the reply. I am really new in this. How do you configure the
> DNS for jenkins to use the URL i want? thanks
>
> On Tue, 23 Oct 2018 at 09:03, Adrien Lecharpentier <
> adrien.lecharpent...@gmail.com> wrote:
>
>> Hello,
>>
>> this is not really enough. This field let you configure how Jenkins will
>> notify the users of the instance, in case of build failure for example.
>>
>> You still need to configure the DNS, reverse-proxy or other elements.
>>
>> Best regards.
>> -- Adrien
>>
>> Le mar. 16 oct. 2018 à 21:58, Faad Sayaou  a écrit :
>>
>>> Hello everyone
>>> I changed Jenkins URL field to "jenkins-app.mywebsite.com" in the
>>> jenkins.model.JenkinsLocationConfiguration.xml file and I tried accessing
>>> it on the browser but to no avail. My goal is to set up a running Jenkins
>>> instance where everyone in the company can access it with the link. Any
>>> help will be appreciated.
>>>
>>> --
>>> 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/b6a0e0ef-6c2b-471c-ac4a-a2927a736abf%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/b6a0e0ef-6c2b-471c-ac4a-a2927a736abf%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Adrien Lecharpentier
>>
>> --
>> 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/CAKwJSvw7v9pMhT0Dz%3DfT_B7-exmmMFZcs9RLg-SbN5gYa%2B2rwA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/CAKwJSvw7v9pMhT0Dz%3DfT_B7-exmmMFZcs9RLg-SbN5gYa%2B2rwA%40mail.gmail.com?utm_medium=email&utm_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/CAL2KjjSTUop73gPV997MgP0edh7v6uVoPp%2BsJYj3inL73-Dk_Q%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAL2KjjSTUop73gPV997MgP0edh7v6uVoPp%2BsJYj3inL73-Dk_Q%40mail.gmail.com?utm_medium=email&utm_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/CAKwJSvxxSdrPvTnA8CBF1tO_smwB3e_exKxcMbV0r6G0%3D04oWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Changing Jenkins URL

2018-10-23 Thread Adrien Lecharpentier
Hello,

this is not really enough. This field let you configure how Jenkins will
notify the users of the instance, in case of build failure for example.

You still need to configure the DNS, reverse-proxy or other elements.

Best regards.
-- Adrien

Le mar. 16 oct. 2018 à 21:58, Faad Sayaou  a écrit :

> Hello everyone
> I changed Jenkins URL field to "jenkins-app.mywebsite.com" in the
> jenkins.model.JenkinsLocationConfiguration.xml file and I tried accessing
> it on the browser but to no avail. My goal is to set up a running Jenkins
> instance where everyone in the company can access it with the link. Any
> help will be appreciated.
>
> --
> 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/b6a0e0ef-6c2b-471c-ac4a-a2927a736abf%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/b6a0e0ef-6c2b-471c-ac4a-a2927a736abf%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Adrien Lecharpentier

-- 
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/CAKwJSvw7v9pMhT0Dz%3DfT_B7-exmmMFZcs9RLg-SbN5gYa%2B2rwA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Jenkins World 2018] - Graders wanted

2018-04-13 Thread Adrien Lecharpentier
I'd be happy to help as well. I submitted a subject to the French CFP, I
don't know if that makes me inadmissible for the review.

-- Adrien

Le ven. 13 avr. 2018 à 20:46, Michael Pailloncy 
a écrit :

> Hi Alyssa,
>
> I would be very happy to help.
>
> Cheers
> Michaël
>
>
> On Fri, Apr 13, 2018 at 6:09 PM, Alyssa Tong  wrote:
>
>> Hello,
>>
>> I am looking for additional graders to join the Jenkins World (JW) review
>> committee to help grade Jenkins World 2018 SF & EU proposals.
>>
>> Time commitment expected:
>>
>>- JW SF: 137 Jenkins submissions.
>>- JW EU: 76 Jenkins submissions at the moment but most likely will
>>increase after close of CFP this Sunday.
>>
>> What you get:
>>
>>- Pix, bio on the Committee webpage (part of JW website)
>>- JW swag
>>- Free conference ticket to JW
>>
>> Criteria:
>>
>>- You love to read and has a keen mind for the latest and greatest,
>>trendy technical topics
>>
>> Pls respond to this thread if you're interested.
>>
>> BR,
>> alyssa
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAC9wNaxGJ-r-Jz%3D1Nyx7otR0TsHEYDPR-V-sR%2B%3D5JRCTsZNbRw%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/CAPO77c1Lu0C4zH%3D7dV1n%3DeDgixovk9LLWdhzGTB8N-HmYKpvdg%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/CAKwJSvxVSJm5vGb4Ls97TXPgHX%3DgBLWRqczL_sB5Wo29_%3DG92A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Stage View for Freestyle Job

2018-03-19 Thread Adrien Lecharpentier
You're not missing something. This is the normal view for a freestyle job.
The stage view for pipeline job (and even BlueOcean) are possible because
the "run" is divided in stages.

This kind of division was not done in freestyle jobs and I'm not sure there
are plans to change the freestyle build view.

Out of curiosity, if you want this stages division, why aren't you moving
to pipeline?

-- Adrien

Le lun. 19 mars 2018 à 09:00, StickSto  a écrit :

> Like I mentioned Pipeline Job show lot's of information but Freestyle's
> basic settings not. Or am I missing something...
> I attach a picture of my Jenkins Freestyle Job's information.
>
> - JH
>
>
> perjantai 16. maaliskuuta 2018 16.19.44 UTC+2 Ullrich Hafner kirjoitti:
>
>> Which information is missing? A freestyle job already has a page for each
>> build with all important post steps.
>>
> Am 16.03.2018 um 14:36 schrieb StickSto :
>>
>> Hello All,
>>
>> Is it possible to get Stage View kind of Result Window to Jenkins's
>> Freestyle Job?
>>
>> Or what kind of Result Windows it's possible to get into Freestyle Job?
>>
>> I would like to use Freestyle Job in my case but it's normal basic Result
>> Window should contain information
>> of it's Builds and Post Build Actions.
>>
>> Can anyone help how to get them, thanks
>>
>> Best Regards,
>>
>> JH
>>
>>
>> --
>> 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/8c5df05a-91aa-4956-a899-883a2a4f8d6a%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/aa66bc3c-f412-4d31-9aa0-406e3860dc02%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/CAKwJSvzJicG59o%2BM%2BUfvURSpXUhz4Rx3hOWJpboCzXdM3KrHqg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: How to run docker commands from jenkins pipeline, permission error

2017-12-29 Thread Adrien Lecharpentier
Is your jenkins user part of the docker group?
-- Adrien

Le ven. 29 déc. 2017 à 13:05, Muhammad Asif  a écrit :

> I have a jenkins pipeline which need to download and create docker image
> on the same machine where jenkins is installed. but I am facing the
> following error.
>
> + docker pull maven:3-alpine
> Warning: failed to get default registry endpoint from daemon (Got permission 
> denied while trying to connect to the Docker daemon socket at 
> unix:///var/run/docker.sock: Get 
> http://%2Fvar%2Frun%2Fdocker.sock/v1.32/info: dial unix /var/run/docker.sock: 
> connect: permission denied). Using system default: https://index.docker.io/v1/
> Got permission denied while trying to connect to the Docker daemon socket at 
> unix:///var/run/docker.sock: Post 
> http://%2Fvar%2Frun%2Fdocker.sock/v1.32/images/create?fromImage=maven&tag=3-alpine:
>  dial unix /var/run/docker.sock: connect: permission denied
>
> --
> 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/34bde1d6-23d5-4def-ab59-cd8075d4691d%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/CAKwJSvy%2B2NnyE8bao%3Dk5cEamRpzD%3DtDfB3V14Ss5EWOr5s%2BrXw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Moving PIpeline global libraries to external SCM

2017-02-28 Thread Adrien Lecharpentier
Once you have"copied" the repo, you can delete the internal repository.
That would remove all possible errors.

Le mar. 28 févr. 2017 à 00:30, Owen Mehegan  a écrit :

> Yeah, that's a good point. But I just wanted to make sure I don't cause
> collisions by having the same classes in the internal and external repos at
> the same time.
> On Feb 27, 2017 2:35 PM, "Mark Waite"  wrote:
>
> Couldn't you use a "git clone" (or git clone --mirror) to copy them to a
> separate repo, then config a remote that would allow you to "git push" them
> to your corporate location?  That will retain the history of the repo and
> the structure (if it matters to you).
>
> Mark Waite
>
> On Mon, Feb 27, 2017 at 3:31 PM Owen B. Mehegan 
> wrote:
>
> I've been using Pipeline global libraries since their inception, storing
> them in the built-in Git server within Jenkins. It's about time that I
> moved them into my company's regular Git repo, where others can collaborate
> on them more easily. What's the right way to do this? Seems like I should
> copy the libraries to the new external repo, then 'git rm' them from the
> existing internal repo, and then configure Jenkins appropriately to pull
> from the external SCM. Am I missing anything else?
>
> --
> 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/07d28411-2272-424a-9ab8-e312799274e5%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/2q1KzxnAtNw/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/CAO49JtEDC_hvG_JposW0zrHXg4QvgQTynCnD8zpgAysvzs19%3DQ%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/CAHtcACFx4%2BgfYLzrHVGfFn6%3DVHyk6jmwSvgtA22MHaSsGp%2B94Q%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/CAKwJSvwC2tKr00GdNgZB5J%3DYkt3JJC2PbSFGUyePyEuLvHUo2w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: How to remove the deleted branch names from "build with parameters"

2017-02-28 Thread Adrien Lecharpentier
Hi,

The orphan branch strategy is for the multibranch kind of job.

What is missing for us here is how do you populate the name of the branches
in the build parameters? This is not automatically done so you must have
either a static list or a groovy script. Please review your job
configuration.

-- Adrien

Le mar. 28 févr. 2017 à 01:27, Jason Yu  a écrit :

>
> Any help for this issue. I upgraded jenkins but the issue still exists.
>
> Thanks.
>
> jason
>
>
> On Thursday, February 23, 2017 at 4:06:13 PM UTC-8, Jason Yu wrote:
>
> I have my jenkins server updated to 2.46 yesterday aiming to resolve this
> issue but it still exists after upgrade.
>
> My jenkins is integrated with our bitbucket account. For each projects, we
> have several branches. When we select "build with parameters" the branches
> name show up. HOwever, even we deleted that branch on bitbucket, the
> deleted bransh name is still showing up. I tried to find the solution
> online to not show these dead branches. but didn't success.
>
> I found some posts mentioned "Orphaned Item Strategy" but in my Jenkins
> UI, I couldn't find it.
>
> Would anyone help me with this? I appreciate any help, thanks.
>
> Jason
>
> --
> 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/ef535d2b-2e92-41e3-a49c-65bb7cae53e8%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/CAKwJSvw8nZxaJRWPV6Tv1MU_3OhUc5Wz1KfNLec6WmUrL%3DFweg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Milestone incompatible with maven release process and recommendations?

2017-02-21 Thread Adrien Lecharpentier
Or you could more simply do a `if (env.BRANCH_NAME == "master"){}` and do
the maven release in this block. Then all you need is to merge into master
to make Jenkins do the release.

Le mar. 21 févr. 2017 à 10:39, Erwan QUEINNEC  a
écrit :

> Thanks Adrien
> Creating a release branch could solve the problem yes.
> But I have to check the impact of the git-flow approach as we have many
> projects and teams using the maven approach...
>
> Le mardi 21 février 2017 10:23:11 UTC+1, Adrien Lecharpentier a écrit :
>
> Hello,
>
> the problem is that milestone is independent of Maven. The release in two
> steps is a maven "problem". What you could do is use the git-flow approach
> and do the real release in separate branch (or in master). You could even
> use https://bitbucket.org/atlassian/jgit-flow/wiki/Home to automate this.
>
> -- Adrien
>
> Le mar. 21 févr. 2017 à 10:06, Erwan QUEINNEC  a
> écrit :
>
> Hi
> If I implement milestone in stage like:
> https://jenkins.io/blog/2016/10/16/stage-lock-milestone/
>
> stage('Build') {
>   milestone()
>   echo "Building"
> }
> stage('Test') {
>   milestone()
>   echo "Testing"
> }
>
> And I execute a release: maven release:prepare -DreleaseVersion=X -Dtag=X
> -DdevelopmentVersion=X-SNAPSHOT
> Jenkins will execute 2 concurrent builds:
> build 1 with pom using version=X=> the release: we want release
> artifacts created and full pipeline
> build 2 with pom using version=SNAPSHOT
> The problem with milestone is jenkins will not execute sometimes the
> release build 1 as build 2 is newer and do not deploy 'release' artifact
> and the full pipeline like a docker image.
> What could be the recommendation using milestone?
> Request could be milestone do not kill 'release' build. Just optimize
> snapshot builds
>
> --
> 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/306bf80c-4144-45a8-ace8-f93dfadf3bef%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/306bf80c-4144-45a8-ace8-f93dfadf3bef%40googlegroups.com?utm_medium=email&utm_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/f12af20b-94fc-4bb5-9c9b-cdbd98b0316b%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/f12af20b-94fc-4bb5-9c9b-cdbd98b0316b%40googlegroups.com?utm_medium=email&utm_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/CAKwJSvx07znyrRfFp9krSmzXfcGHajFyiEB8NZcdkJW%3DE9oQNQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Milestone incompatible with maven release process and recommendations?

2017-02-21 Thread Adrien Lecharpentier
Hello,

the problem is that milestone is independent of Maven. The release in two
steps is a maven "problem". What you could do is use the git-flow approach
and do the real release in separate branch (or in master). You could even
use https://bitbucket.org/atlassian/jgit-flow/wiki/Home to automate this.

-- Adrien

Le mar. 21 févr. 2017 à 10:06, Erwan QUEINNEC  a
écrit :

> Hi
> If I implement milestone in stage like:
> https://jenkins.io/blog/2016/10/16/stage-lock-milestone/
>
> stage('Build') {
>   milestone()
>   echo "Building"
> }
> stage('Test') {
>   milestone()
>   echo "Testing"
> }
>
> And I execute a release: maven release:prepare -DreleaseVersion=X -Dtag=X
> -DdevelopmentVersion=X-SNAPSHOT
> Jenkins will execute 2 concurrent builds:
> build 1 with pom using version=X=> the release: we want release
> artifacts created and full pipeline
> build 2 with pom using version=SNAPSHOT
> The problem with milestone is jenkins will not execute sometimes the
> release build 1 as build 2 is newer and do not deploy 'release' artifact
> and the full pipeline like a docker image.
> What could be the recommendation using milestone?
> Request could be milestone do not kill 'release' build. Just optimize
> snapshot builds
>
> --
> 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/306bf80c-4144-45a8-ace8-f93dfadf3bef%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/CAKwJSvy21yeFSyrCYXPp_qJbgr%3DqMcjr5548VT7s%2BruQQmJBDA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.