Re: Unknown Workflow CPS Exceptions in Jenkins log

[Mark Waite]

PI Plugin 2.10
> Pipeline: SCM Step 2.7
> Pipeline: Shared Groovy Libraries 2.13
> Pipeline: Stage Tags Metadata 1.3.4.1
> Pipeline: Stage View Plugin 2.10
> Pipeline: Step API 2.19
> Pipeline: Supporting APIs 3.2
> Git client plugin 2.7.6
> Git Parameter 0.9.9
> Git Pipeline for Blue Ocean 1.11.1
> Git plugin 3.9.3
> SCM API Plugin <http://wiki.jenkins-ci.org/display/JENKINS/SCM+API+Plugin> 
> 2.3.0
>
> --
> 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/184cfd95-5cbe-4a82-8d5f-d50caefe9be8%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/184cfd95-5cbe-4a82-8d5f-d50caefe9be8%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Re: Windows Installation and AIX slave.

[Mark Waite]

Yes, if you install Java 8 on AIX, you are likely able to run an agent
there.  Jenkins agents run on many architectures that support Java 8.

On Tue, Feb 19, 2019 at 10:04 AM Patrick Hamm  wrote:

> Hello Forum;
>
> I am new in Jenkins world and I have a project in the collegue, can be
> possible to install Jenkins in a windows server and then, Can I have access
> to AIX ? I am thinking like a kind of AIX slave,
>
> Regards.
>
> --
> 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/c3f9e95e-a7c1-47d2-8659-8b55e6cf40ae%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/c3f9e95e-a7c1-47d2-8659-8b55e6cf40ae%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Re: jenkins.repo of the redhat-stable not updated correctly for the new 2.150.3 release?

[Mark Waite]

There was an infrastructure issue which blocked the publication of the
rpm.  That issue has been resolved, but the release has not yet been pushed
to the repository.

On Tue, Feb 19, 2019 at 1:49 AM Johan Compagner 
wrote:

> ok checked it my self by looking how a yum repo works and this file:
>
>
> https://pkg.jenkins.io/redhat-stable/repodata/ba942e34ac1b0daaadea909c4d89536c81a553865f4242074892abb0c0276595-filelists.xml.gz
>
> really only has 2.150.2 as the latest release. So the repo is really not
> updated
>
>
> Op dinsdag 19 februari 2019 09:37:27 UTC+1 schreef Johan Compagner:
>>
>> Hi,
>>
>> until now if there was a new release i just could do "yum update" on my
>> redhat system and the installation found and updated to the new release
>> with ease.
>>
>> But this new release 2.150.3 is just not found, i tried clearing caches
>> and stuff like that, but it always just says no updates..
>>
>> Is there something wrong in the repo configuration?
>>
>> Johan
>>
> --
> 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/8c083f8e-0a11-4587-b6c6-de63a500f5bd%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/8c083f8e-0a11-4587-b6c6-de63a500f5bd%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Re: Need help unsubscribing

[Mark Waite]

Unfortunately, I can't find your original e-mail address or any variant of
it in the google groups.

I see 4 owners for the group and 4 managers (different people than the
owners).  When I search for your first name "Jeremie", I see only a listing
that says you joined 2 hours ago.  I assume that is using your new address,
not your old address.  I can't find your old address to delete it.

I don't see e-mail addresses in the query.  I believe Google intentionally
hides e-mail addresses so that group administrators won't misuse them.

Is there another name that you might have used rather than "Jeremie" or
"jeremie"?

On Mon, Feb 18, 2019 at 12:03 PM Jeremie Faucher-Goulet <
jeremie.faucher-gou...@trilliant.com> wrote:

> Hi guys/owner/admin.
>
> I find myself in a bit of a bind/catch-22 and don’t know how to proceed
> without the group’s admin/owner involvement.
>
> Both Google Support and my local IT department have been unable to help me
> thus far.
>
>
>
> How can I unsubscribe from the group when my domain name has changed, and
> emails are now being forwarded to my new address?
>
>1. I can’t email jenkinsci-users+unsubscr...@googlegroups.com. My
>request is not recognized because the email originator (the “FROM” field)
>gets overwritten by Microsoft servers to my new email address as it goes
>along its merry way over the internets.
>2. I can’t create a Google Account using my old address because it
>contains a hyphen “-“ and Google considers that an illegal character for
>email addresses. If I could create a Google Account, I would have been able
>to manage my group subscriptions myself apparently.
>
>
>
> It seems, according to Google’s “expert”, that my only option is to ask
> the owner/admin to remove me from the group. I tried doing so without
> getting a response. His latest suggestion was for me to mail the entire
> group to get an admin’s attention.
>
> Here is the discussion I had with Google Support =>
> https://productforums.google.com/forum/#!topic/apps/whhIUPPEZDI
>
>
>
> All this trouble because Outlook 365 Is putting the group (and other
> groups) messages addressed to my old email address in quarantine, making it
> an unreadable mess defeating the purpose of a quarantine if I no longer can
> look/skim through it. I’ve missed important emails because of this. And I
> can’t configure Outlook’s “Safe Senders” for an email address that is no
> longer mine.
> I have already subscribed using with my new email address so I can post
> and receive emails, but I still need my old subscriptions to be removed to
> remove all that traffic in my quarantine.
>
> Any help/hints would be highly appreciated.
>
>
>
> FYI, my email address changed in the following manner:
>
> jeremie.faucher-gou...@trilliantinc.com ->
> jeremie.faucher-gou...@trilliant.com
>
>
>
> And I’m sorry for polluting everyone’s mailbox with this,
>
>
>
> Jeremie
>
> --
> 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/BN8PR06MB5539C4B0653ED6622AA5A8A8DC630%40BN8PR06MB5539.namprd06.prod.outlook.com
> <https://groups.google.com/d/msgid/jenkinsci-users/BN8PR06MB5539C4B0653ED6622AA5A8A8DC630%40BN8PR06MB5539.namprd06.prod.outlook.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

-- 
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/CAO49JtFsbkF5K%2B%3D6%2B0prH%3D3CeL_0ndGtoqaSombf4VAOji9_Rw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Does Bitbucket Source Branch plugin support "SSH username with private key" type credentials?

[Mark Waite]

I suspect that it is using API calls that are not available through an ssh
connection.

On Thu, Feb 14, 2019, 6:19 PM Cameron Morrison  Hi,
>
> I am using the bitbucket-source-branch plugin - it's working, but I cannot
> figure out how to provide "SSH & private key" type credentials to the
> branch source, when using the Bitbucket source type.
>
> It does work with username/password authentication, and a bare Git type
> branch source *does* work with SSH and private key, but the Birbucket
> source type does not show any SSH credentials at all. Is there something I
> am missing? Or does the plugin simply not support the SSH and private key
> credential type for Bitbucket branch sources?
>
> Cheers,
> Cameron Morrison
>
>
> --
> 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/f835484d-311f-4d3d-90d9-24cc5a2d143c%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/CAO49JtHibZVHkOY0vHsitnX4j%3Df1bOGLXfMJrXzv1Qiqz01yPg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: What are the reasons for using "Merging the pull request with the current target branch revision"

[Mark Waite]

You may be able to reduce clone times by using a reference repository when
performing the checkout from your pipeline.  I've found that an explicitly
declared checkout significantly reduces the network data transfer and the
disc usage when I have a reference repository on the agent and on the
master.

https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-43931/Jenkinsfile
shows an example in a scripted Pipeline.

Mark Waite

On Thu, Feb 14, 2019 at 6:59 AM Viacheslav Dubrovskyi 
wrote:

>
> 14.02.2019 12:58, Steven Foster пишет:
> > It would definitely be my preferred way of building code, but
> > unfortunately the Jenkins master has to clone and perform the merge
> > per pipeline every time. That doesn't scale on a sizeable repo with
> > many active PRs and 12 multibranch pipelines :(
>
> Agree. And you must clone the repository at least 2 times. The first
> time to get Jenkinsfile, the second for tests. It is very annoying. It
> would be convenient to somehow be able to use previously cloned code.
>
>
> --
>
> WBD,
> Viacheslav Dubrovskyi
>
>
> --
> 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/fd12342e-b2a3-e6b4-18a8-44a79aa22041%40gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Re: Jenkins is throwing exception error for robot sikuli script

[Mark Waite]

Since SIkuli is a screen capture and replay based testing framework, it
needs access to the Windows desktop.  Running as a Windows service does not
give access to the Windows desktop by default.

I suggest that you should configure a dedicated Windows machine that is
logged into the Desktop automatically when Windows starts and automatically
starts the JNLP based agent to connect to the Jenkins server.  Assign a
label to that agent (maybe 'sikuli') and run your sikuli tests on that
agent.

There are other techniques that attempt to give Windows desktop access to a
Windows service.   I'm not persuaded that they are worth the effort.
Windows services generally are not expected to interact with the Windows
desktop.

Mark Waite

On Thu, Feb 14, 2019 at 3:06 AM Sayali Waghmare 
wrote:

> Hi,
>
> I have a robot sikuli script when run from terminal it just runs fine.
>
> When executed from jenkins as a job it is throwing a exception as 
> om.github.rainmanwy.robotframework.sikulilib.exceptions.TimeoutException:
> Timeout happend, could not find P(signin.PNG) S: 0.7.
>
> Jenkins is installed as a service on windows machine.
>
> Attached are the logs.
>
> 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/2a3aa4be-8594-4a6e-92d5-07a8e2b215a0%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/2a3aa4be-8594-4a6e-92d5-07a8e2b215a0%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Re: Does the SSH Agents plugin support FIPS 140-2?

[Mark Waite]

My recollection from previous times was that FIPS-140-2 compliant
implementations must be "certified".  I thought that required that a
FIPS-140-2 implementation had to be purchased and included into the product
that was intended to be FIPS-140-2 compliant.  Jenkins has not purchased a
FIPS-140-2 compliant library.  It uses open source implementations of
cryptographic algorithms.

However, my exposure to that requirement was quite brief and may be
entirely incorrect.

Mark Waite

On Wed, Feb 13, 2019 at 11:43 AM Dunnigan (US), Terrence J <
terrence.j.dunni...@boeing.com> wrote:

> Thanks for the suggestion! We tried it and the ssh command said it wasn’t
> allowed to use ed25519 in FIPS mode. We’ve connected via JNLP so perhaps
> the issue has been sidestepped.
>
>
>
> Thanks again,
>
>
>
> Terry
>
>
>
> *From:* jenkinsci-users@googlegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Mark Waite
> *Sent:* Monday, February 11, 2019 1:55 PM
> *To:* Jenkins Users 
> *Subject:* Re: Does the SSH Agents plugin support FIPS 140-2?
>
>
>
> Try with an ed25519 private key. Some online docs suggest that ed25519 is
> FIPS-140-2 approved.
>
>
>
> On Mon, Feb 11, 2019, 12:13 PM Dunnigan (US), Terrence J <
> terrence.j.dunni...@boeing.com wrote:
>
> Hi all,
>
>
>
> Does the SSH Slaves plugin support FIPS 140-2 (
> https://en.wikipedia.org/wiki/FIPS_140-2) ? In my case I have a Windows
> VM running Jenkins trying to connect to a RHEL7 VM with FIPs enabled. I’m
> getting SSH authentication errors, and the RHEL logs suggest that the
> Jenkins SSH Slaves plugin is not using a FIPS-approved protocol.
>
>
>
> Thanks,
>
>
>
> Terry
>
> --
> 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/d8563d21c76647e3ba72cedb130194b7%40boeing.com
> <https://groups.google.com/d/msgid/jenkinsci-users/d8563d21c76647e3ba72cedb130194b7%40boeing.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtE01W915PZv3BMPEJWfrzbKgFDRTWt%2BZw%3DwFmYJPYYPWA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtE01W915PZv3BMPEJWfrzbKgFDRTWt%2BZw%3DwFmYJPYYPWA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/f3d19fd5ecef40cf90150a95b688394d%40boeing.com
> <https://groups.google.com/d/msgid/jenkinsci-users/f3d19fd5ecef40cf90150a95b688394d%40boeing.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Re: Does the SSH Agents plugin support FIPS 140-2?

[Mark Waite]

Try with an ed25519 private key. Some online docs suggest that ed25519 is
FIPS-140-2 approved.

On Mon, Feb 11, 2019, 12:13 PM Dunnigan (US), Terrence J <
terrence.j.dunni...@boeing.com wrote:

> Hi all,
>
>
>
> Does the SSH Slaves plugin support FIPS 140-2 (
> https://en.wikipedia.org/wiki/FIPS_140-2) ? In my case I have a Windows
> VM running Jenkins trying to connect to a RHEL7 VM with FIPs enabled. I’m
> getting SSH authentication errors, and the RHEL logs suggest that the
> Jenkins SSH Slaves plugin is not using a FIPS-approved protocol.
>
>
>
> Thanks,
>
>
>
> Terry
>
> --
> 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/d8563d21c76647e3ba72cedb130194b7%40boeing.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/CAO49JtE01W915PZv3BMPEJWfrzbKgFDRTWt%2BZw%3DwFmYJPYYPWA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins is running as a docker image in a kubernetes cluster and won't come up due to plugin version incompatibility

[Mark Waite]

The docker image uses the file 'plugins.txt' to select the plugin versions
to use.  You can modify the plugins.txt file to change the versions of
plugins used in the docker image.

On Mon, Feb 11, 2019 at 6:37 AM आलोक कुमार  wrote:

> We are running Jenkins as a docker image in a kubernetes cluster. However
> it does not come up any more because of some plugin version
> incompatibility. How can we upgrade the plugins, or disable them to bring
> up Jenkins?
>
> Note that because Jenkins is not up, we cannot upgrade / disable plugins
> with the Jenkins UI.
>
> --
> 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/2cdfaf6c-5ec1-4162-8e6b-a68a990c1061%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/2cdfaf6c-5ec1-4162-8e6b-a68a990c1061%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Re: How to configure $JENKINS_HOME/caches dir location?

[Mark Waite]

Used by multibranch pipeline and possibly by pipeline as far as I recall.

On Fri, Feb 8, 2019, 5:52 PM Calvin Park  It seems to contain some sort of git cache. Thankfully(?) all the
> directories are empty.
>
>> /mnt/nfs/jenkins_home$ ls caches/
>> git-0d341dcbcc7c33c4efc44a104b892b60
>> git-79660c3529cacbdbe1ac71b7c36e1a3f
>> git-0d341dcbcc7c33c4efc44a104b892b60@tmp
>> git-79660c3529cacbdbe1ac71b7c36e1a3f@tmp
>> git-0fba0b0ccfb8c3ca2809f860ea497fbf
>> git-84f1d58c7f2dde1b560bd3471e85cf5f
>> git-0fba0b0ccfb8c3ca2809f860ea497fbf@tmp
>> git-84f1d58c7f2dde1b560bd3471e85cf5f@tmp
>> git-117076ea5a481ebdd2beea321164041c
>> git-93d0b594de0d6af9e1ac33ea8dd03742
>> git-117076ea5a481ebdd2beea321164041c@tmp
>> git-93d0b594de0d6af9e1ac33ea8dd03742@tmp
>> git-20faeeea626404c43e0af02b3443a0ca
>> git-bedd02d2756f33f2b6dd8e496041e9a5
>> git-20faeeea626404c43e0af02b3443a0ca@tmp
>> git-bedd02d2756f33f2b6dd8e496041e9a5@tmp
>> git-663a4358cb957136aec86030ea76
>> git-ca5af9d29c97e0a07af654ef31dbcd93
>> git-663a4358cb957136aec86030ea76@tmp
>> git-cde48c33a9866d69b3dab200ae527b91
>> git-6c18e173e843c139db9b4bcd2949c277
>> git-cde48c33a9866d69b3dab200ae527b91@tmp
>> git-6c18e173e843c139db9b4bcd2949c277@tmp
>> git-ea66c44ab8389abea26eb7f2f93ee8d0
>> git-72cee31ae083a2db1f8fb009bcf624ed
>> git-ea66c44ab8389abea26eb7f2f93ee8d0@tmp
>> git-72cee31ae083a2db1f8fb009bcf624ed@tmp
>
>
>
> In order to minimize the performance hit from putting jenkins_home on NFS,
> I'm trying to find the directories which are frequently accessed
> directories and has many small files
>
>> /mnt/nfs/jenkins_home$ ls -d */
>> .cache/  ?
>> .groovy/ ?
>> .java/   ?
>> caches/  ?
>> config-history/
>> fingerprints/
>> init.groovy.d/
>> jobs/
>
>  builds/ moved out to local disk and not backed up
>>  workspace/  moved out to local disk and not backed up
>
> logs/
>>
> nodes/
>> plugins/   moved out to local disk and not backed up
>> secrets/
>> updates/
>> userContent/
>> users/
>> war/   moved out to local disk and not backed up
>> workflow-libs/
>>
>
> What are some of the other directories in here that I can/should move out
> of NFS? Ideally they should be ephemeral and frequently accessed.
>
> Thank you
>
>
>
> On Tuesday, February 5, 2019 at 6:08:46 AM UTC-8, Baptiste Mathus wrote:
>>
>> I've had a quick look, and I'm not sure I ever saw a caches directory
>> under JENKINS_HOME (this is very possible I just don't remember).
>> Can you possibly list what's in there so we can try and understand what
>> is generating this directory?
>>
>> We segregate data quite aggressively already in Evergreen and I do not
>> remember of such a directory/option.
>>
>> https://github.com/jenkins-infra/evergreen/blob/master/distribution/Dockerfile#L22-L34
>>
>> Thanks
>>
>> Le dim. 3 févr. 2019 à 00:44, Calvin Park  a écrit :
>>
>>> I'm running $JENKINS_HOME on NFS. Due to the performance penalty,
>>> I want to move out as many temp directories as I can to local disk.
>>>
>>> Thus far I've moved
>>>
>>>-
>>>
>>> -Djenkins.model.Jenkins.workspacesDir='/local_cache/workspace/${ITEM_FULL_NAME}'
>>>- --webroot=/local_cache/web
>>>- --pluginroot=/local_cache/plugin
>>>
>>> In $JENKINS_HOME there's caches directory which seems like an obvious
>>> choice to move out.
>>>
>>>1. Is there a way to configure the location for $JENKINS_HOME/caches?
>>>2. What are other directories that can be recreated, thus can be
>>>moved out of the NFS?
>>>
>>> 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/6a923fd6-da83-484e-b57c-c899e08a56f3%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/998a1e68-9e5a-48e2-b1eb-389e6b5b4652%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 

Re: Remove config Git Clïent plugin in Global Tool Configuration

[Mark Waite]

No, there is not a way to remove the global configuration of an installed
plugin.

You might be able to write a system groovy script that performs the delete
action on each startup.

I've never tried that, but it might be possible. It seems like a lot of
work to remove an item from the config UI.

Mark Waite

On Thu, Feb 7, 2019, 8:06 AM  Hi,
>
> We don't use this plugin, but because of dependency it can't be removed.
> Therefore this plugin appears in the Global Tool Configuration. When i push
> on the button to delete git, the config disapears as expected, but when i
> restart Jenkins the Git config appears again.
> Is there a way to remove this config permanently?
>
> With kind regards, Wil
>
> --
> 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/1eff02d4-4cf9-4331-998e-cc46cb233a7c%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/1eff02d4-4cf9-4331-998e-cc46cb233a7c%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHT15PKwCEiMy714k1OEJ_6GjXXxbaE5gY4Q5GRdLv%3D4A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Unable to run git repository on jenkins which is deplyed under tomcat8

[Mark Waite]

On Fri, Feb 1, 2019 at 5:10 AM Archana Srichandan <
archana.srichan...@4tigo.com> wrote:

> Hi,
>  Thanks for your reply. I gave the url as serverip:path to repository, The
> username is given as the user of the remote server to which to do SSH. I
> have created a private key for the user which I am logged in into the
> jenkins server. I am copying the private key directly and also the
> passphrase. Still I am not able to clone from the repository. Please let me
> know if I am doing something wrong.
> Note. Jenkins is running behind tomcat. (I deploy jenkins through tomcat).
>

Does the passphrase include characters which are special to the shell (like
'#', '*', '(', or ')')?  If so, use a private key with a passphrase that
does not include characters that are special to the shall.  The current git
client plugin implementation has a problem with shell special characters in
passphrases.

Mark Waite


> Regards,
> Archana Srichandan
>
>
> On Thu, Jan 31, 2019 at 8:58 PM Mark Waite 
> wrote:
>
>> Did you assign a private key credential to that job?  A username.password
>> credential won't work with an SSH URL.  A private key credential won't work
>> with an http or https URL.
>>
>> If the private key has a passphrase, did you provide the passphrase when
>> defining the credential in Jenkins?
>>
>> Did you confirm that the private key will authenticate from the command
>> line?
>>
>> Mark Waite
>>
>> On Tue, Jan 29, 2019 at 3:17 PM  wrote:
>>
>>> Hi All,
>>>
>>> I am not able to run my git repo on Jenkins ,attach is the screen shot
>>> for your reference.
>>>
>>> Regards,
>>> Archana Srichandan
>>>
>>> --
>>> 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/50dd7ccf-9ad6-45e3-a5fc-9cee050a7737%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/50dd7ccf-9ad6-45e3-a5fc-9cee050a7737%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Thanks!
>> Mark Waite
>>
>> --
>> 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/CAO49JtGvL%3DxHGju7a%2BbGvVd7Bhs7gvhr09Qd%3Dr3zkY1OOs2DhA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGvL%3DxHGju7a%2BbGvVd7Bhs7gvhr09Qd%3Dr3zkY1OOs2DhA%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CA%2BU8sbXkPabE0ZqNTq_iur%3DRGjmm6MeaYdzXgRPCNMsqfheS_A%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CA%2BU8sbXkPabE0ZqNTq_iur%3DRGjmm6MeaYdzXgRPCNMsqfheS_A%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Re: Unable to run git repository on jenkins which is deplyed under tomcat8

[Mark Waite]

Did you assign a private key credential to that job?  A username.password
credential won't work with an SSH URL.  A private key credential won't work
with an http or https URL.

If the private key has a passphrase, did you provide the passphrase when
defining the credential in Jenkins?

Did you confirm that the private key will authenticate from the command
line?

Mark Waite

On Tue, Jan 29, 2019 at 3:17 PM  wrote:

> Hi All,
>
> I am not able to run my git repo on Jenkins ,attach is the screen shot for
> your reference.
>
> Regards,
> Archana Srichandan
>
> --
> 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/50dd7ccf-9ad6-45e3-a5fc-9cee050a7737%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/50dd7ccf-9ad6-45e3-a5fc-9cee050a7737%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Re: How to push to Gitlab after Jenkins build

[Mark Waite]

On Sun, Jan 27, 2019 at 2:14 PM Faad Sayaou  wrote:

> 0
>
> I have a stage at the end of my pipeline job which has to push changes
> back to a particular Gitlab branch. After trying out several solutions
> proposed on stackoverflow, I am still not able to push to the branch
>
> sh("git add .")
> sh("git commit -a -m ' New changes'")
> sh('git push https://${GIT_USERNAME}:${GIT_PASSWORD}@ ')
>
> I expected it to be pushed to the branch which it checked out from but I
> get the following result on the console
>
>- git commit -a -m ' New changes' [detached HEAD bc78567] New changes
>- Everything up-to-date
>
> any reason for this issue?
>

The git plugin default behavior is to checkout without creating a branch.
That is why the output of `git commit` includes `detached HEAD ...`.

That made it easier to switch between different commits on different
branches from inside a single workspace.  That was a common use model with
Freestyle jobs.  It is not a common use model with Pipeline jobs.

Because there is no branch defined in the workspace, git cannot infer the
destination branch to which the changes should be pushed.  You can pass an
additional argument to `git push` which tells it to push the HEAD revision
to the specific named branch you want.  For example, if the remote
destination branch is named 'master', the command would be:

git push https://${GIT_USERNAME}:${GIT_PASSWORD}@ HEAD:master

 Mark Waite

> --
> 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/00dbb024-1cb8-47f5-bdb5-255c3e2f0907%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/00dbb024-1cb8-47f5-bdb5-255c3e2f0907%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Re: Error Message : org.xmlpull.v1.XmlPullParserException: only 1.0 is supported as

[Mark Waite]

ava:904)
>>>>at hudson.model.Hudson.(Hudson.java:85)
>>>>at hudson.model.Hudson.(Hudson.java:81)
>>>>at hudson.WebAppMain$3.run(WebAppMain.java:231)
>>>> Caused: hudson.util.HudsonFailedToLoad
>>>>at hudson.WebAppMain$3.run(WebAppMain.java:248)
>>>>
>>>>
>>>> Regards,
>>>> Poovaraj
>>>>
>>>> --
>>>> 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/cf6d78d2-6495-4801-8efa-915c3e532153%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-users/cf6d78d2-6495-4801-8efa-915c3e532153%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-use...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6bjbspVHppJQn7YCcJbsPhr1iMWEZxxqCVmaKG3z1Vug%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6bjbspVHppJQn7YCcJbsPhr1iMWEZxxqCVmaKG3z1Vug%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/7738900f-9f4e-46c1-8e72-f3f68cdca402%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/7738900f-9f4e-46c1-8e72-f3f68cdca402%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Re: Error installing automatically JDK 8u192

[Mark Waite]

Yes, it can be downloaded locally and distributed as a "JDK tool" defined 
in the "Global tool configuration" of "Manage Jenkins".  However, I was 
reminded by Arnaud Heritier some time ago that downloading it and 
distributing it locally may be a violation of the Oracle license agreement 
or the Oracle terms and conditions.

With the increasing visibility of OpenJDK, I'm moving more and more to 
depend on OpenJDK builds rather than Oracle builds.  I don't violate 
OpenJDK license agreements when I cache a copy of their installer locally.

Mark Waite

On Thursday, January 17, 2019 at 10:23:50 AM UTC-7, bnext...@gmail.com 
wrote:
>
> It started working today, it looks like it was an issue with the website 
> of Oracle.  Could the file be downloaded manually and be provided in a 
> local path to Jenkins somehow?
>
> On Wednesday, January 16, 2019 at 4:21:53 PM UTC-6, bnext...@gmail.com 
> wrote:
>>
>> Hi,
>>
>> While updating the JDK automatically to the latest available of Java 
>> 8(192 it is showing an error when running a job.
>>
>> Jenkins Version 2.157
>> Runtime Java: 1.8.0_191-b12
>> OS: Windows Server 2012 R2
>>
>> Log:
>> [EnvInject] - Loading node environment variables.
>> Installing JDK jdk-8u192-oth-JPR
>> Downloading JDK from 
>> https://download.oracle.com/otn-pub/java/jdk/8u192-b12/750e1c8617c5452694857ad95c3ee230/jdk-8u192-windows-x64.exe
>> ERROR: SEVERE ERROR occurs
>> org.jenkinsci.lib.envinject.EnvInjectException: java.io.IOException: 
>> Failed to request 
>> https://download.oracle.com/otn-pub/java/jdk/8u192-b12/750e1c8617c5452694857ad95c3ee230/jdk-8u192-windows-x64.exe?AuthParam=1547661233_86512d6bbec0aa3bfeb252b1e1926a6a
>>  
>> exit code=404
>> at 
>> org.jenkinsci.plugins.envinject.util.RunHelper.getBuildVariables(RunHelper.java:137)
>> at 
>> org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironmentWithoutJobPropertyObject(EnvInjectListener.java:235)
>> at 
>> org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:51)
>> at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:542)
>> at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:462)
>> at hudson.model.Run.execute(Run.java:1810)
>> at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
>> at hudson.model.ResourceController.execute(ResourceController.java:97)
>> at hudson.model.Executor.run(Executor.java:429)
>> Caused by: java.io.IOException: Failed to request 
>> https://download.oracle.com/otn-pub/java/jdk/8u192-b12/750e1c8617c5452694857ad95c3ee230/jdk-8u192-windows-x64.exe?AuthParam=1547661233_86512d6bbec0aa3bfeb252b1e1926a6a
>>  
>> exit code=404
>> at hudson.tools.JDKInstaller.locate(JDKInstaller.java:492)
>> at hudson.tools.JDKInstaller.performInstallation(JDKInstaller.java:150)
>> at 
>> hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:72)
>> at 
>> hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:109)
>> at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:206)
>> at hudson.model.JDK.forNode(JDK.java:148)
>> at 
>> org.jenkinsci.plugins.envinject.util.RunHelper.getJDKVariables(RunHelper.java:111)
>> at 
>> org.jenkinsci.plugins.envinject.util.RunHelper.getBuildVariables(RunHelper.java:135)
>> ... 8 more
>>
>> Any recommendation to fix the issue?
>>
>

-- 
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/e91149a5-cad0-4bb7-86ec-423ac7cd357a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Remote call on JNLP4-connect connection

[Mark Waite]

That stack trace seems like an out of memory condition on an agent or on
the master.  I think I'd first try disconnecting and reconnecting the
agent.  I'd also check the JDK versions on the agent and the master are
reasonably close to one another.

Mark Waite

On Mon, Jan 14, 2019 at 5:51 PM LnT  wrote:

> Reinstall Jenkins and slave
>
> On Tue 15 Jan, 2019, 1:05 AM Sangeetha Guhan 
>> Any resolution for this issue? Please help.
>>
>> On Tuesday, 17 October 2017 06:46:13 UTC-7, LnT wrote:
>>>
>>> *Hi,*
>>>
>>> * Our Jenkins ver. 2.46.1 <http://jenkins-ci.org/>*
>>> *project configuration is working till yesterday. all of sudden start
>>> failing.*
>>>
>>>
>>> *Precisely , project does below things*
>>> *1. Fetch code from git lab*
>>> *2. Fetch code from external site using npm*
>>> *3. create and deploys the package*
>>>
>>> *project fails - even before step#1 *
>>> *Please find below console log. **Could someone please help.*
>>>
>>>  Building remotely on slav1 in workspace D:\JenkinsSlv\workspace\RTM
>>>  FATAL: java.io.IOException: Remote call on JNLP4-connect connection
>>> from slav1.applications.com/10.112.17.119:53814 failed
>>>  java.lang.OutOfMemoryError: PermGen space
>>>   at sun.misc.Unsafe.defineClass(Native Method)
>>>   at sun.reflect.ClassDefiner.defineClass(Unknown Source)
>>>   at sun.reflect.MethodAccessorGenerator$1.run(Unknown Source)
>>>   at sun.reflect.MethodAccessorGenerator$1.run(Unknown Source)
>>>   at java.security.AccessController.doPrivileged(Native Method)
>>>   at sun.reflect.MethodAccessorGenerator.generate(Unknown Source)
>>>   at
>>> sun.reflect.MethodAccessorGenerator.generateSerializationConstructor(Unknown
>>> Source)
>>>   at
>>> sun.reflect.ReflectionFactory.newConstructorForSerialization(Unknown Source)
>>>   at java.io.ObjectStreamClass.getSerializableConstructor(Unknown Source)
>>>   at java.io.ObjectStreamClass.access$1500(Unknown Source)
>>>   at java.io.ObjectStreamClass$2.run(Unknown Source)
>>>   at java.io.ObjectStreamClass$2.run(Unknown Source)
>>>   at java.security.AccessController.doPrivileged(Native Method)
>>>   at java.io.ObjectStreamClass.(Unknown Source)
>>>   at java.io.ObjectStreamClass.lookup(Unknown Source)
>>>   at java.io.ObjectOutputStream.writeObject0(Unknown Source)
>>>   at java.io.ObjectOutputStream.writeArray(Unknown Source)
>>>   at java.io.ObjectOutputStream.writeObject0(Unknown Source)
>>>   at java.io.ObjectOutputStream.defaultWriteFields(Unknown Source)
>>>   at java.io.ObjectOutputStream.writeSerialData(Unknown Source)
>>>   at java.io.ObjectOutputStream.writeOrdinaryObject(Unknown Source)
>>>   at java.io.ObjectOutputStream.writeObject0(Unknown Source)
>>>   at java.io.ObjectOutputStream.writeObject(Unknown Source)
>>>   at hudson.remoting.UserRequest._serialize(UserRequest.java:190)
>>>   at hudson.remoting.UserRequest.serialize(UserRequest.java:199)
>>>   at hudson.remoting.UserRequest.(UserRequest.java:64)
>>>   at hudson.remoting.Channel.call(Channel.java:828)
>>>   at
>>> hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:257)
>>>   at com.sun.proxy.$Proxy65.setProxy(Unknown Source)
>>>   at
>>> org.jenkinsci.plugins.gitclient.RemoteGitImpl.setProxy(RemoteGitImpl.java:873)
>>>   at org.jenkinsci.plugins.gitclient.Git.getClient(Git.java:140)
>>>   at hudson.plugins.git.GitSCM.createClient(GitSCM.java:751)
>>>  Caused: java.io.IOException: Remote call on JNLP4-connect connection
>>> from slav1.applications.com/10.112.17.119:53814 failed
>>>   at hudson.remoting.Channel.call(Channel.java:838)
>>>   at
>>> hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:257)
>>>  Caused: hudson.remoting.RemotingSystemException
>>>   at
>>> hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:273)
>>>   at com.sun.proxy.$Proxy65.setProxy(Unknown Source)
>>>   at
>>> org.jenkinsci.plugins.gitclient.RemoteGitImpl.setProxy(RemoteGitImpl.java:873)
>>>   at org.jenkinsci.plugins.gitclient.Git.getClient(Git.java:140)
>>>   at hudson.plugins.git.GitSCM.createClient(GitSCM.java:751)
>>>   at hudson.plugins.git.GitSCM.createClient(GitSCM.java:743)
>>>   at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1101)
>>>   at hudson.scm.SCM.checkout(SCM.java:496)
>>>   at hudson.model.Ab

Re: How to get GIT revision. All kind of post on variables does not match any case.

[Mark Waite]

If GIT_COMMIT is not providing what you want, then you can use an `sh` or
`bat` step to get the sha1 of the commit that is the HEAD of the working
repository.

See
https://github.com/MarkEWaite/jenkins-pipeline-utils/blob/fa3266f738f735e40581abfd9b6a226b3dac0ab6/pipelineSteps.groovy#L41
for an example.

Mark Waite



On Mon, Jan 14, 2019 at 12:40 PM Eldad Cohen  wrote:

> How to get GIT revision in a pipeline. All kind of post on variables does
> not match any case.
>
> --
> 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/262a2b3d-efac-4980-9607-5ae37712eb34%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/262a2b3d-efac-4980-9607-5ae37712eb34%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Bug report or question to the mailing list

[Mark Waite]

Gregor Philp has a question that he'll need to ask the mailing list.  He 
started by appending the question to another bug report.  The user mailing list 
is a better place for questions.

Thanks,
Mark Waite (from a non-standard account)

-- 
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/MWHPR13MB158158937229D18AE75744B4BD8B0%40MWHPR13MB1581.namprd13.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

Re: SSH Connection failed with IOException: "Connection timed out (Connection timed out)" - Jenkins Remote Agent Connectivity

[Mark Waite]

Some things you might check (based on the connection timeout error message):

   - Is the OpenSSH server feature installed on the Windows Server that
   you're connecting? (Windows -> Manage Features)
   - Is the OpenSSH server enabled on the Windows Server? (Windows ->
   Services)
   - Is the OpenSSH network port (22) accessible on the Windows Server from
   the Jenkins master?  (Try 'ssh localhost' from a command prompt on the
   Windows server, then 'ssh your-server-name' from another host)

Once you've confirmed that those things are correct and working as
expected, then you might try the workaround that I used to connect a
Windows agent to a Jenkins master using ssh.  Refer to my comment in
JENKINS-42856
<https://issues.jenkins-ci.org/browse/JENKINS-42856?focusedCommentId=355486=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-355486>
for the details.

On Sat, Dec 29, 2018 at 8:47 AM Poovaraj Thangamariappan <
poovaraj2...@gmail.com> wrote:

> Hi,
>
> Jenkins is not connecting remote agent through SSH. It is showing below
> error message. Can you please help me to fix this?
>
> *Error Message:-*
>
> [image: Remote Agenet Connectivity Issue.PNG]
>
> *Configuration :-*
>
> [image: Jenkins Remote Agent Connectivy Config 1.PNG]
>
> [image: Jenkins Remote Agent Connectivy Config 2.PNG]
> --
>
> Regards,
> Poovaraj
>
>
> --
> 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/CAMu9-ZUkd-6W4bbGSbxDadX0UsV6qKJ2q57ja4MBeSKOvpum-w%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAMu9-ZUkd-6W4bbGSbxDadX0UsV6qKJ2q57ja4MBeSKOvpum-w%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Re: Resurrecting a Backup to SCM structure - with Jenkinsfile and Agents

[Mark Waite]

I use a private docker image for rapid Jenkins test setup and teardown.  In 
that private image, I place copies of relevant files in the "ref/" 
directory.  That allows me to copy credentials, job definitions, folder 
definitions, etc.

I plan to eventually move away from that technique since it embeds 
credentials into my Docker image, but I haven't found the next technique.  
I suspect it will involve storing the credentials in the Kubernetes 
credentials store rather than placing them in the docker repo.

Mark Waite

On Tuesday, December 25, 2018 at 12:42:44 PM UTC-7, Randall Becker wrote:
>
> Hi All,
>
> Following best practices, we moved our entire build structure to a 
> per-project Jenkinsfile and agents where the various parts of builds 
> happen. The Jenkinsfiles are stored in the git repositories involved and we 
> are using multi-branch projects. All that is working file.
>
> Our issue is that our Jenkins runs inside docker and the node 
> configuration, certificates, and Jenkins system configuration is not yet 
> stored in an SCM environment. We want that to happen so that we can restore 
> Jenkins quickly from scratch if something happens, without having to go 
> through the trouble of recreating the Agent structure from scratch and 
> redefining the multibranch jobs. We've had a newbie or two (me as an 
> example) accidentally blow out the docker config and lost our Jenkins Agent 
> structure.
>
> It seems like the Configuration-as-Code plugin might work, but it is hard 
> to get a sense that this can configure Jenkins in its entirety or whether 
> we can take the existing configuration and import/convert it to that 
> plugin, and how config moves in and out of it.
>
> Any Sense of this?
>
> Thanks,
> Randall
>

-- 
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/00163293-05ed-4792-9629-18b43cfcc648%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Unable to Launch an Agent, getting "received junk text is as follows: stdin: is not a tty"

[Mark Waite]

I inserted diagnostic print messages into my bashrc at almost every line so
that I could tell exactly which line was causing the problem.  It was a
coarse technique that helped me quickly detect the problem commands

On Fri, Dec 21, 2018 at 12:37 PM Philippe M. 
wrote:

> Thanks,
> That's what I started to do , but how to find all of them ?
> Do you have a tip ?
>
> Thanks
>
> On Friday, December 21, 2018 at 6:12:50 PM UTC+1, Mark Waite wrote:
>>
>> You'll need to remove the entries in the '.profile' and/or '.bashrc' that
>> are doing things which are not allowed in a non-interactive shell.  Either
>> that, or wrap them in conditionals which prevent them from being executed
>> in a non-interactive shell.
>>
>> Mark Waite
>>
>> On Friday, December 21, 2018 at 9:20:26 AM UTC-7, Philippe M. wrote:
>>>
>>> Hello,
>>>
>>> We are facing an issue using Jenkins 2.138.3 and connecting to certain
>>> machines (issue occurs with machines in  redhat 7.2, not in 6.4 but not
>>> sure it's related).
>>>
>>> When we start the agent, we get this error, issue being that ssh gives 
>>> "stdin:
>>> is not a tty"
>>>
>>> Full Jenkins log:
>>>
>>> SSHLauncher{host='XXX.XXX.X.XXX', port=22,
>>> credentialsId='XXX', jvmOptions='', javaPath='',
>>> prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=210,
>>> maxNumRetries=10, retryWaitTime=15,
>>> sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.KnownHostsFileKeyVerificationStrategy,
>>> tcpNoDelay=true, trackCredentials=true}
>>>
>>> [12/21/18 16:41:19] [SSH] Opening SSH connection to XXX.XXX.X.XXX:22.
>>>
>>> [12/21/18 16:41:19] [SSH] SSH host key matches key in Known Hosts file.
>>> Connection will be allowed.
>>>
>>> [12/21/18 16:41:19] [SSH] Authentication successful.
>>>
>>> SSH connection reports a garbage before a command execution.
>>>
>>> Check your .bashrc, .profile, and so on to make sure it is quiet.
>>>
>>> The received junk text is as follows:
>>>
>>> stdin: is not a tty
>>>
>>>
>>>
>>> null
>>>
>>> [12/21/18 16:41:20] Launch failed - cleaning up connection
>>> [12/21/18 16:41:20] [SSH] Connection closed.
>>>
>>>
>>> How can this be fixed, searching for similar issues, I see fixes related
>>> to sudoers but we are not sudoing here.
>>> I also found issue could be triggered by Banner , but there is no banner
>>> either.
>>>
>>> Note that if we try non interactive mode, we have this which explains
>>> the issue faced by Jenkins I guess:
>>>
>>> ssh -T login@host:
>>> stty: standard input: Inappropriate ioctl for device
>>> stdin: is not a tty
>>> stdin: is not a tty
>>> stdin: is not a tty
>>>
>>>
>>> I tried to disable in /etc/profile stty if in non interactive mode, it
>>> fixed :
>>>
>>> stty: standard input: Inappropriate ioctl for device
>>>
>>> So I now have:
>>>
>>> ssh -T login@host:
>>> stdin: is not a tty
>>> stdin: is not a tty
>>> stdin: is not a tty
>>>
>>> But I am stuck here.
>>>
>>> Thanks in advance for your help.
>>> Regards
>>>
>>> --
> 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/1e6f8395-c7c3-4151-ade6-1efeef217aff%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/1e6f8395-c7c3-4151-ade6-1efeef217aff%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Re: Unable to Launch an Agent, getting "received junk text is as follows: stdin: is not a tty"

[Mark Waite]

You'll need to remove the entries in the '.profile' and/or '.bashrc' that 
are doing things which are not allowed in a non-interactive shell.  Either 
that, or wrap them in conditionals which prevent them from being executed 
in a non-interactive shell.

Mark Waite

On Friday, December 21, 2018 at 9:20:26 AM UTC-7, Philippe M. wrote:
>
> Hello,
>
> We are facing an issue using Jenkins 2.138.3 and connecting to certain 
> machines (issue occurs with machines in  redhat 7.2, not in 6.4 but not 
> sure it's related).
>
> When we start the agent, we get this error, issue being that ssh gives 
> "stdin: 
> is not a tty" 
>
> Full Jenkins log:
>
> SSHLauncher{host='XXX.XXX.X.XXX', port=22, 
> credentialsId='XXX', jvmOptions='', javaPath='', 
> prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=210, 
> maxNumRetries=10, retryWaitTime=15, 
> sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.KnownHostsFileKeyVerificationStrategy,
>  
> tcpNoDelay=true, trackCredentials=true}
>
> [12/21/18 16:41:19] [SSH] Opening SSH connection to XXX.XXX.X.XXX:22.
>
> [12/21/18 16:41:19] [SSH] SSH host key matches key in Known Hosts file. 
> Connection will be allowed.
>
> [12/21/18 16:41:19] [SSH] Authentication successful.
>
> SSH connection reports a garbage before a command execution.
>
> Check your .bashrc, .profile, and so on to make sure it is quiet.
>
> The received junk text is as follows:
>
> stdin: is not a tty
>
>  
>
> null
>
> [12/21/18 16:41:20] Launch failed - cleaning up connection
> [12/21/18 16:41:20] [SSH] Connection closed.
>
>
> How can this be fixed, searching for similar issues, I see fixes related 
> to sudoers but we are not sudoing here.
> I also found issue could be triggered by Banner , but there is no banner 
> either.
>
> Note that if we try non interactive mode, we have this which explains the 
> issue faced by Jenkins I guess:
>
> ssh -T login@host:
> stty: standard input: Inappropriate ioctl for device
> stdin: is not a tty
> stdin: is not a tty
> stdin: is not a tty
>
>
> I tried to disable in /etc/profile stty if in non interactive mode, it 
> fixed :
>
> stty: standard input: Inappropriate ioctl for device
>
> So I now have:
>
> ssh -T login@host:
> stdin: is not a tty
> stdin: is not a tty
> stdin: is not a tty
>
> But I am stuck here.
>
> Thanks in advance for your help.
> Regards
>
>

-- 
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/d04c9c12-3d62-4acd-904d-5e9f6087ab83%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Unable to checkout Jenkinsfile from git for a Pipeline Job: getting unable to fork

[Mark Waite]

On Friday, December 21, 2018 at 7:06:06 AM UTC-7, Mark Waite wrote:
>
>
>
> On Friday, December 21, 2018 at 6:20:56 AM UTC-7, Philippe M. wrote:
>>
>> Hello,
>>
>> Using Jenkins 2.138.3 and Git client plugin 2.7.4 I get an error when 
>> doing the following:
>>
>> 1) Create job of type Pipeline
>> 2) Select pipeline from SCM and enter 
>> - ssh://g...@bitbucket.example.com:7999/~userXXX/jmt_poc.git 
>> <http://g...@bitbucket.foo.com:7999/~userXXX/jmt_poc.git>
>> - Credentials come from a private key
>>
>> 3) Build job , it fails with:
>>
>> Started by user unknown or anonymous
>> Checking out git ssh://
>> g...@bitbucket.example.com:7999/~userXXX/jmt_poc.git 
>> <http://www.google.com/url?q=http%3A%2F%2Fgit%40bitbucket.foo.com%3A7999%2F~userXXX%2Fjmt_poc.git=D=1=AFQjCNGYzuIbpxwau3cIrbdtwVKAQX-kLQ>
>>  
>> into /var/lib/jenkins/workspace/POC_JMT_PIPELINE_FROM_GIT2@script to read 
>> Jenkinsfile
>> Cloning the remote Git repository
>> Cloning repository ssh://
>> g...@bitbucket.example.com:7999/~userXXX/jmt_poc.git 
>> <http://www.google.com/url?q=http%3A%2F%2Fgit%40bitbucket.foo.com%3A7999%2F~userXXX%2Fjmt_poc.git=D=1=AFQjCNGYzuIbpxwau3cIrbdtwVKAQX-kLQ>
>> > git init /var/lib/jenkins/workspace/POC_JMT_PIPELINE_FROM_GIT2@script # 
>> timeout=10
>> Fetching upstream changes from ssh://
>> g...@bitbucket.example.com:7999/~userXXX/jmt_poc.git 
>> <http://www.google.com/url?q=http%3A%2F%2Fgit%40bitbucket.foo.com%3A7999%2F~userXXX%2Fjmt_poc.git=D=1=AFQjCNGYzuIbpxwau3cIrbdtwVKAQX-kLQ>
>> > git --version # timeout=10
>> using GIT_SSH to set credentials
>>  > git fetch --tags --progress ssh://
>> g...@bitbucket.example.com:7999/~userXXX/jmt_poc.git 
>> <http://www.google.com/url?q=http%3A%2F%2Fgit%40bitbucket.foo.com%3A7999%2F~userXXX%2Fjmt_poc.git=D=1=AFQjCNGYzuIbpxwau3cIrbdtwVKAQX-kLQ>
>>  
>> +refs/heads/*:refs/remotes/origin/*
>> ERROR: Error cloning remote repo 'origin'
>> hudson.plugins.git.GitException: Command "git fetch --tags --progress 
>> ssh://g...@bitbucket.example.com:7999/~userXXX/jmt_poc.git 
>> <http://www.google.com/url?q=http%3A%2F%2Fgit%40bitbucket.foo.com%3A7999%2F~userXXX%2Fjmt_poc.git=D=1=AFQjCNGYzuIbpxwau3cIrbdtwVKAQX-kLQ>
>>  
>> +refs/heads/*:refs/remotes/origin/*" returned status code 128:
>> stdout:
>> stderr: fatal: cannot exec 
>> '/var/lib/jenkins/workspace/POC_JMT_PIPELINE_FROM_GIT2@script@tmp/ssh7220368723599186680.sh':
>>  
>> Permission denied
>> fatal: unable to fork
>>at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2016)
>>at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1735)
>>at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:72)
>>at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:420)
>>at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:629)
>>at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1146)
>>at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186)
>>at 
>> org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120)
>>at 
>> org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:144)
>>at 
>> org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:67)
>>at 
>> org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:292)
>>at 
>> hudson.model.ResourceController.execute(ResourceController.java:97)
>>at hudson.model.Executor.run(Executor.java:429)
>> ERROR: Error cloning remote repo 'origin'
>> ERROR: Maximum checkout retry attempts reached, aborting
>> Finished: FAILURE
>>
>> Master is running on redhat 7.2, openjdk 1.8.0_65 64 bit server VM 
>>
>>
> Check that the temporary directory on the master is not mounted with the 
> 'noexec' option.  Check that the workspace directory on the master is not 
> mounted with the 'noexec' option.
>
> The Jenkins git client plugin needs to communicate credentials to command 
> line git.  Red Hat Linux defaults to an old enough version of command line 
> git that the only way to communicate those credentials is through an 
> executable shell script.  The executable shell script is placed in a 
> temporary directory on the master and run from the master.  The preferred 
> location for 

Re: Unable to checkout Jenkinsfile from git for a Pipeline Job: getting unable to fork

[Mark Waite]

On Friday, December 21, 2018 at 6:20:56 AM UTC-7, Philippe M. wrote:
>
> Hello,
>
> Using Jenkins 2.138.3 and Git client plugin 2.7.4 I get an error when 
> doing the following:
>
> 1) Create job of type Pipeline
> 2) Select pipeline from SCM and enter 
> - ssh://g...@bitbucket.example.com:7999/~userXXX/jmt_poc.git 
> <http://g...@bitbucket.foo.com:7999/~userXXX/jmt_poc.git>
> - Credentials come from a private key
>
> 3) Build job , it fails with:
>
> Started by user unknown or anonymous
> Checking out git ssh://g...@bitbucket.example.com:7999/~userXXX/jmt_poc.git 
> <http://www.google.com/url?q=http%3A%2F%2Fgit%40bitbucket.foo.com%3A7999%2F~userXXX%2Fjmt_poc.git=D=1=AFQjCNGYzuIbpxwau3cIrbdtwVKAQX-kLQ>
>  
> into /var/lib/jenkins/workspace/POC_JMT_PIPELINE_FROM_GIT2@script to read 
> Jenkinsfile
> Cloning the remote Git repository
> Cloning repository ssh://
> g...@bitbucket.example.com:7999/~userXXX/jmt_poc.git 
> <http://www.google.com/url?q=http%3A%2F%2Fgit%40bitbucket.foo.com%3A7999%2F~userXXX%2Fjmt_poc.git=D=1=AFQjCNGYzuIbpxwau3cIrbdtwVKAQX-kLQ>
> > git init /var/lib/jenkins/workspace/POC_JMT_PIPELINE_FROM_GIT2@script # 
> timeout=10
> Fetching upstream changes from ssh://
> g...@bitbucket.example.com:7999/~userXXX/jmt_poc.git 
> <http://www.google.com/url?q=http%3A%2F%2Fgit%40bitbucket.foo.com%3A7999%2F~userXXX%2Fjmt_poc.git=D=1=AFQjCNGYzuIbpxwau3cIrbdtwVKAQX-kLQ>
> > git --version # timeout=10
> using GIT_SSH to set credentials
>  > git fetch --tags --progress ssh://
> g...@bitbucket.example.com:7999/~userXXX/jmt_poc.git 
> <http://www.google.com/url?q=http%3A%2F%2Fgit%40bitbucket.foo.com%3A7999%2F~userXXX%2Fjmt_poc.git=D=1=AFQjCNGYzuIbpxwau3cIrbdtwVKAQX-kLQ>
>  
> +refs/heads/*:refs/remotes/origin/*
> ERROR: Error cloning remote repo 'origin'
> hudson.plugins.git.GitException: Command "git fetch --tags --progress 
> ssh://g...@bitbucket.example.com:7999/~userXXX/jmt_poc.git 
> <http://www.google.com/url?q=http%3A%2F%2Fgit%40bitbucket.foo.com%3A7999%2F~userXXX%2Fjmt_poc.git=D=1=AFQjCNGYzuIbpxwau3cIrbdtwVKAQX-kLQ>
>  
> +refs/heads/*:refs/remotes/origin/*" returned status code 128:
> stdout:
> stderr: fatal: cannot exec 
> '/var/lib/jenkins/workspace/POC_JMT_PIPELINE_FROM_GIT2@script@tmp/ssh7220368723599186680.sh':
>  
> Permission denied
> fatal: unable to fork
>at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2016)
>at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1735)
>at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:72)
>at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:420)
>at 
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:629)
>at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1146)
>at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1186)
>at 
> org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120)
>at 
> org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:144)
>at 
> org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:67)
>at 
> org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:292)
>at 
> hudson.model.ResourceController.execute(ResourceController.java:97)
>at hudson.model.Executor.run(Executor.java:429)
> ERROR: Error cloning remote repo 'origin'
> ERROR: Maximum checkout retry attempts reached, aborting
> Finished: FAILURE
>
> Master is running on redhat 7.2, openjdk 1.8.0_65 64 bit server VM 
>
>
Check that the temporary directory on the master is not mounted with the 
'noexec' option.  Check that the workspace directory on the master is not 
mounted with the 'noexec' option.

The Jenkins git client plugin needs to communicate credentials to command 
line git.  Red Hat Linux defaults to an old enough version of command line 
git that the only way to communicate those credentials is through an 
executable shell script.  The executable shell script is placed in a 
temporary directory on the master and run from the master.  The preferred 
location for that temporary directory is adjacent to the workspace 
directory.  However, there are cases where the system temporary directory 
is used instead.

Refer to https://issues.jenkins-ci.org/browse/JENKINS-26993 
and https://issues.jenkins-ci.org/browse/JENKINS-44951 for much more detail 
on the topic.

Mark Waite
 

> If I create a project from content of Jenkinsfile directly , which 
> checkouts exactly the same repository , it works fine but node is o

Re: How to add a secret file?

[Mark Waite]

I think you want the "plain credentials
<https://plugins.jenkins.io/plain-credentials>" plugin.

On Thu, Dec 20, 2018 at 8:27 AM Benjamin Primrose  wrote:

> Hi everyone, noob here.  I’ve got a functioning install, and need a secret
> file to provide passwords to a build.  When I access
> Credentials->System->Global credentials->Add Credentials, the “Kind”
> drop-down only lists “Username with password” and “SSH Username with
> private key”.  Searching turns up a few hundred “it’s easy to use a secret
> file” articles, but all assume the option for a file is in the drop-down.
> Can someone point me to the relevant documentation?
>
>
>
> Benjamin Primrose
> Principal Developer
> • Fitchburg, MA 01420
>
> Ph:978-353-8054 • bprimr...@wcu.com
>
>
>
>
>
> *Confidentiality Notice:  The materials in this electronic mail
> transmission (including attachments) are private and confidential and are
> the property of the sender and Workers Credit Union.  Unless stated to the
> contrary, any opinions or comments are personal to the writer and do not
> represent the official view of Workers Credit Union.  If you are not the
> intended recipient, you are hereby notified that any use, dissemination,
> disclosure or copying of this communication is strictly prohibited.  If you
> have received this communication in error, please destroy all copies of
> this message and its attachments and notify us immediately.  Thank you.*
>
>
>
> --
> 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/5c1bb251.1c69fb81.47b4e.5104SMTPIN_ADDED_MISSING%40gmr-mx.google.com
> <https://groups.google.com/d/msgid/jenkinsci-users/5c1bb251.1c69fb81.47b4e.5104SMTPIN_ADDED_MISSING%40gmr-mx.google.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Re: ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.

[Mark Waite]

You might check that the job definition was not changed recently.  If that
shows nothing of interest, you could login to the workspace last used for
the clone and perform the same commands in that clone.  That may help
identify what is failing.

On Mon, Dec 17, 2018 at 1:11 PM 'Yash Dabhi' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:

> Hi Mark,
>
> Thanks for the reply.
>
> I tried cloning the branch in my local and it clones fine. Branch exists
> and able to commit as well. Not sure why it stopped working suddenly.
>
> Thanks,
> Yash
>
> On Monday, December 17, 2018 at 2:40:41 PM UTC-5, Mark Waite wrote:
>>
>> That seems to indicate that you previously had a branch named '9' and now
>> the branch named '9' no longer exists.
>>
>> Mark Waite
>>
>> On Mon, Dec 17, 2018 at 11:32 AM 'Yash Dabhi' via Jenkins Users <
>> jenkins...@googlegroups.com> wrote:
>>
>>> Hi all,
>>>
>>> when I am trying to run job getting below error. Getting this while
>>> checking out the source code.
>>>
>>> It happened all of sudden. I was working fine with the same
>>> configuration.
>>>
>>> Please advise what can be done.
>>>
>>> > git fetch --tags ssh://${git_url}.git CICD
>>>  > git rev-parse refs/remotes/origin/9^{commit} # timeout=10
>>>  > git rev-parse refs/remotes/origin/origin/9^{commit} # timeout=10
>>>  > git rev-parse origin/9^{commit} # timeout=10ERROR: Couldn't find any 
>>> revision to build. Verify the repository and branch configuration for this 
>>> job.An attempt to send an e-mail to empty list of recipients, ignored.
>>> [BFA] Scanning build for known causes...
>>> [BFA] Found failure cause(s):
>>> [BFA] GIT Revision Error from category SCM
>>> [BFA] Done. 0s
>>>
>>>
>>>
>>> Thank you!
>>>
>>>
>>> --
>>> 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/68dc0a47-6c28-4027-8fa2-ed6c3e6a5492%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/68dc0a47-6c28-4027-8fa2-ed6c3e6a5492%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Thanks!
>> Mark Waite
>>
> --
> 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/a02980bc-c27f-4515-bd65-d9405af2b3e4%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/a02980bc-c27f-4515-bd65-d9405af2b3e4%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

-- 
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/CAO49JtEPyqyNStin%2BiT2UG0sNc2k1H1saZb%3D%2BPwnSTDX43%3DDow%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.

[Mark Waite]

That seems to indicate that you previously had a branch named '9' and now
the branch named '9' no longer exists.

Mark Waite

On Mon, Dec 17, 2018 at 11:32 AM 'Yash Dabhi' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:

> Hi all,
>
> when I am trying to run job getting below error. Getting this while
> checking out the source code.
>
> It happened all of sudden. I was working fine with the same configuration.
>
> Please advise what can be done.
>
> > git fetch --tags ssh://${git_url}.git CICD
>  > git rev-parse refs/remotes/origin/9^{commit} # timeout=10
>  > git rev-parse refs/remotes/origin/origin/9^{commit} # timeout=10
>  > git rev-parse origin/9^{commit} # timeout=10ERROR: Couldn't find any 
> revision to build. Verify the repository and branch configuration for this 
> job.An attempt to send an e-mail to empty list of recipients, ignored.
> [BFA] Scanning build for known causes...
> [BFA] Found failure cause(s):
> [BFA] GIT Revision Error from category SCM
> [BFA] Done. 0s
>
>
>
> Thank you!
>
>
> --
> 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/68dc0a47-6c28-4027-8fa2-ed6c3e6a5492%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/68dc0a47-6c28-4027-8fa2-ed6c3e6a5492%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Re: How to configure GitHub Organizaiton Item/Job via Groovy

[Mark Waite]

Since you're already starting from a JENKINS_HOME directory, you may find
it easier to store the job definition rather than attempting to create the
job from a groovy script.  Refer to
https://github.com/MarkEWaite/docker-lfs/blob/lts-slim-with-plugins/ref/jobs/Git-Client-Folder/jobs/git-client-pipeline-github/config.xml
for an example in a Docker image.

Mark Waite

On Fri, Dec 14, 2018 at 2:46 PM Phillip Dudley 
wrote:

> Would anyone have any pointers to configuring the GitHub Organization
> Item/Job with Groovy so that when my Jenkins instance starts up, it reads
> the
>
> $JENKINS_HOME/init.groovy.d/
>
> folder and configures a default job to perform GitHub Organization
> scanning for Jenkinsfiles?
>
> I've got most of the other stuff I need such as setting banners,
> installing plugins, configuring default Jenkins users and assigning them
> permissions via the matrix-auth plugin. Even finally hooked up to LDAP and
> I can authenticate. However, I don't seem to find too much on configuring
> that plugin except through the UI. Most of my Googling returns results for
> using Jenkinsfiles, or Groovy tutorials, but not actually setting up and
> configuring that plugin.
>
> TL;DR,
> Looking for a direction to learn how to configure the GitHub Organization
> job to scan my GitHub Organization for Jenkinsfiles and start performing
> Jobs.
>
> --
> 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/e59e3c84-27e5-4c47-a4f9-20e76860ef2f%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/e59e3c84-27e5-4c47-a4f9-20e76860ef2f%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Re: java.io.IOException: remote file operation failed

[Mark Waite]

Refer 
to 
https://wiki.jenkins.io/display/JENKINS/Builds+failing+with+OutOfMemoryErrors 
for pointers.  If your server or build agent is macOS, refer to the comment 
from Alexander Link about unable to create new native thread.

If that doesn't resolve it, refer 
to https://wiki.jenkins.io/display/JENKINS/I%27m+getting+OutOfMemoryError.

On Thursday, December 13, 2018 at 9:51:05 AM UTC-7, pbasan...@gmail.com 
wrote:
>
> Hi ,
> Jenkins Job failing with 
>
> ava.lang.OutOfMemoryError: unable to create new native thread
>   at java.lang.Thread.start0(Native Method)
>   at java.lang.Thread.start(Thread.java:717)
>
>
> aused: java.io.IOException: Remote call on JNLP4-connect connection from 
> slc13lde.us.oracle.com/10.247.90.202:39472 failed
>   at hudson.remoting.Channel.call(Channel.java:913)
>   at hudson.FilePath.act(FilePath.java:987)*Caused: java.io.IOException: 
> remote file operation failed: /scratch/syseng/workspace/ProductLayerPublisher 
> at *hudson.remoting.Channel@71d1d2c2:JNLP4-connect connection from 
> slc13lde.us.oracle.com/10.247.90.202:39472
>   at hudson.FilePath.act(FilePath.java:994)
>
>
> Can you please suggest what could be the cause of this issue.
>
>
> Regards,
>
> Basanta
>
>
>

-- 
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/ba3fbe11-5a01-4374-9d87-c8951a8f97b8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: running shell commands in pipeline fails on pushd and source

[Mark Waite]

That seems to hint that the shell invoked on that agent by the Pipeline
script is not compatible with the shell syntax you're using.

For example, is the shell on that agent inadvertently configured to be
'dash' instead of 'bash'?  Is it configured to be 'csh' instead of 'bash'?

https://askubuntu.com/questions/590899/how-to-check-which-shell-am-i-using
suggests that you might run a test job with an sh 'echo $0' or with sh
'echo $SHELL'

On Fri, Dec 7, 2018 at 6:36 AM 'Carsten' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:

> Hi list,
>
> in a jenkinsfile I trigger a bash script like so:
> "...
> myresult=sh(script: 'deploy.sh', returnStdout: true)
> ..."
> the script starts but returns errors like these:
>
> "command not found: pushd"
> "command not found: source"
>
> And for some reasons it is not able to do such things:
> "...
> targetmachine=(
> 'host1'
> 'host2'
> 'host3'
> )
> ..."
>
> it replies: Syntax error: "(" unexpected.
>
> Other commands like "if", "for", "echo", a.s.o are working.
>
> The script itself is tested on the machine, where jenkins is running, and
> it works.
> Jenkins is installed as docker image "docker pull jenkins:jenkins".
> The Image is started as "root" using "sudo docker run"
> Does anybody have an idea why these commands and the array creation fails?
>
> br
> Carsten
>
> --
> 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/a2181b6e-96cc-4182-abca-a8ae0a0e195f%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/a2181b6e-96cc-4182-abca-a8ae0a0e195f%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Re: Jenkins Backup and Restore

[Mark Waite]

He's saying that if you don't need to backup and restore your job
definitions (possibly they are all multibranch Pipeline jobs that are easy
to recreate, or they are all defined with the Job DSL plugin so they will
be automatically recreated or they are defined in a Docker image) and don't
need to backup and restore your credential definitions (same reasons) and
don't need to backup and restore other configuration settings (possibly
because you're using Configuration as Code plugin to store your
configuration in a source control system), then there are backup concepts
that use a source control system as your backup system.

In your use case, I suspect you want to use a backup.

Mark Waite

On Tue, Nov 27, 2018 at 7:50 AM  wrote:

> I'm not sure what you are trying to say?
>
> On Monday, November 26, 2018 at 8:03:34 PM UTC-5, rajendraprasad reddy
> wrote:
>>
>> Hi ,
>> I have another solution, just document the list of plugins in old Jenkins
>> server and instead of backup and restore plugins just reinstall plugins on
>> new Jenkins server.
>>
>> Thanks,
>> Rajendra
>>
>> On Fri, 2 Nov, 2018, 02:06 >
>>> We have a Jenkins instance running and we are trying to setup a backup
>>> and restore mechanism in case of any mishaps.  We are looking for a full
>>> backup of the Jenkins and so decided to go with PeriodicBackup plugin.
>>> With this plugin, the backup works fine.  But, we are trying to restore it
>>> in a completely new Jenkins setup and not able to restore.  When we pick
>>> the backup file that we want to restore from, it says restoring, but
>>> nothing happens.  Even after waiting out for over 30 mins, nothing is
>>> restored.  As a work around, I stopped the Jenkins service, renamed the
>>> 'JENKINS_HOME' (/var/lib/jenkins) folder to 'jenkins_backup' and created
>>> another folder called 'jenkins' in the same location.  In this folder, I
>>> copied all the files from the backup and then started Jenkins (NOTE: I
>>> didn't change the .owner file.  I'm using the .owner file of the new
>>> Jenkins only).  Jenkins came up and I was able to see all the
>>> configurations from the old one.  Everything was fine.  I let it like that
>>> overnight and in the morning when I came and tried to access it, Jenkins
>>> was way too slow and I was not able to save any new configuration.  When I
>>> try I'm getting
>>> java.io.ioexception: too many open files jenkins
>>> error.  I restarted the jenkins and it's taking too long for the UI to
>>> come up.  Am I doing anything wrong here?  Any suggestions for my
>>> requirement?
>>>
>>> P.S. - I tried SCMSync plugin and ThinBackup.  But, problem with these
>>> are that they don't do full backup.  But, with ThinBackup both backup and
>>> restore works fine.
>>>
>>> --
>>> 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/0c58b4fa-4e8b-4c53-9ca9-b99397078fae%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/0c58b4fa-4e8b-4c53-9ca9-b99397078fae%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/9d3fad8e-7bbe-4472-86dd-57ef3d0da960%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/9d3fad8e-7bbe-4472-86dd-57ef3d0da960%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

-- 
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/CAO49JtH-ydL8JkmnFurJ06s%2BEn-b%3DWaNmb_KT%3DBFiz6mbZK8QQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: how to find how a Jenkins instance is installed?

[Mark Waite]

I'm not aware of any direct method from inside Jenkins that will report how
it was installed.  There are differences in the file system layout from the
various installation techniques which could be used to guess which
installer was used.

For example:

   - If /etc/default/jenkins exists, then it is likely an 'apt' based
   installation (like Debian and Ubuntu)
   - If /etc/sysconfig/jenkins exists, then it is likely an 'rpm' based
   installation (like Red Hat Enterprise Linux and CentOS)

I don't know the details of installations on macOS, OpenSUSE, FreeBSD,
OpenBSD, AIX, s390x, or OpenIndiana.

Mark Waite

On Mon, Nov 19, 2018 at 7:07 AM  wrote:

> I apologize for the delay in responding.  Just got chance to check back on
> these.
>
> Yes Mark, you are right.  I'm trying to determine if Jenkins was installed
> from apt/yum, rpm, MSI or war file.  Is there a way to find how the
> installation was done?
>
> On Wednesday, November 14, 2018 at 10:02:17 PM UTC-5, Mark Waite wrote:
>>
>> I thought the question was trying to determine if the Jenkins
>> installation was done from apt, rpm, MSI, chocolatey, or using a war file.
>> Interesting the different assumptions we make to a question.
>>
>> Can the original questioner clarify what they were asking?
>>
>> On Wed, Nov 14, 2018 at 7:33 PM Martin d'Anjou 
>> wrote:
>>
>>> If you mean how do you test if an instance is ready (after a restart),
>>> you can use curl.
>>>
>>> httpCode=$(curl -s -w "%{http_code}" -X GET $JENKINS_URL)
>>> while [[  $httpCode != "200" ]]; do
>>> sleep 5
>>> httpCode=$(curl -s -w "%{http_code}" -X GET $JENKINS_URL)
>>> done
>>> echo "Jenkins is ready."
>>>
>>>
>>> On Wednesday, November 14, 2018 at 10:03:44 AM UTC-5, gotvi...@gmail.com
>>> wrote:
>>>>
>>>> Hello, how do I find out how a Jenkins instance has been installed?
>>>>
>>> --
>>> 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/70b0817f-aa60-42cc-bd83-713742c305aa%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/70b0817f-aa60-42cc-bd83-713742c305aa%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Thanks!
>> Mark Waite
>>
> --
> 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/d1f4d4b2-5f77-49f1-afe7-20a06aa503dc%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/d1f4d4b2-5f77-49f1-afe7-20a06aa503dc%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Re: Multibranch Pipeline Scan Hangs

[Mark Waite]

My working bitbucket.org multibranch Pipeline configurations include:

   - Bitbucket branch source (username / password authentication)
   - Git branch source using https (username / password authentication)
   - Git branch source using ssh (ed25519 private key with passphrase)

Will your corporate standards allow use of a username and password over
https?  If so, does that behave any better in your environment?

Mark Waite

On Thu, Nov 15, 2018 at 7:28 PM Randall Becker 
wrote:

> I have 2 idle executors on every node, so that's not it. The hang is
> definitely waiting on a response from git fetch or git ls-remote depending
> on the situation. Version of git on the Ubuntu VM is 2.13, so that's not
> particularly recent, but sufficient for the function being executed. I
> cannot get this to work on any instance of any VM I have. Of note, there
> are no specific instructions other than the basic setup of the job (monitor
> the repo, run ls-remote, and finish). Perhaps with some instructions it
> might behave differently. When I interrupt the job, the job name is "null",
> which is suspect and wrong.
>
> I've gone to non-multibranch pipelines, as assume that this particular
> plugin is DOA - sorry about the opinion, but I cannot make it work, despite
> all efforts, so will not recommend it. If there is a working configuration,
> please describe it, and I'll try to make it work as specified. $DAYJOB
> forces me away from this approach.
>
> On Thursday, November 15, 2018 at 6:09:26 PM UTC-5, Meg Watson wrote:
>>
>> I’ll take a stab...How many executors do you have on the master and
>> agent?  You may be hanging waiting for an executor to be available to run
>> the pipeline.  I think I made this mistake once, had too few executors.
>>
>> Meg
>
> --
> 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/a2538d76-8460-40bf-861c-57bff009df27%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/a2538d76-8460-40bf-861c-57bff009df27%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Re: Multibranch Pipeline Scan Hangs

[Mark Waite]

My passing tests were run from a master running in Docker with agents
running a mix of various operating systems including Windows, Linux
(CentOS, Debian, Ubuntu), and FreeBSD.

Mark Waite

On Thu, Nov 15, 2018 at 3:21 PM Randall Becker 
wrote:

> I will continue to investigate. I am wondering whether there might be
> something associated with running Jenkins in docker with Controller/Agent
> structure.
>
> On Thursday, November 15, 2018 at 5:18:31 PM UTC-5, Mark Waite wrote:
>>
>> I created a multibranch Pipeline with bitbucket.org as the source using
>> Git as the branch source with a passphrase protected ed25519 private key.
>> It scans and builds as expected.
>>
>> I can't duplicate the problem that you're describing.  Before you spend
>> the time to submit a bug report, you may want to duplicate the bug in a
>> different environment, just in case there is something specific in your
>> environment that is different than my attempt to duplicate the problem.
>>
>> Bug reports for the project are submitted to
>> https://issues.jenkins-ci.org/ .
>>
>> On Thu, Nov 15, 2018 at 3:11 PM Mark Waite  wrote:
>>
>>> I created a multibranch pipeline with bitbucket.org as the source using
>>> the Bitbucket Branch Source plugin.  That plugin prompted for a username /
>>> password rather than a private key.  It won't accept a private key.  I
>>> believe it uses REST APII calls to reduce the overhead of checking for new
>>> branches and for changes in the existing branches.  Since the REST API is
>>> based on https, it needs username / password rather than a private key.
>>>
>>> The Bitbucket Branch Source plugin provides additional capabilities
>>> because it is aware of Bitbucket, rather than being limited to those
>>> components which are generic git operations.
>>>
>>> Is there a reason you're not using the Bitbucket Branch Source plugin,
>>> rather than using the Git branch source?
>>>
>>> On Thu, Nov 15, 2018 at 12:24 PM Randall Becker 
>>> wrote:
>>>
>>>> There is also similar hang at fetch when the Jenkinsfile SCM is used.
>>>> It does appear that the credentials may not be supplied properly but there
>>>> is no indication that this is the case. I'm dropping back to Simple
>>>> Pipelines without SCM, sadly. This rather makes the whole point rather
>>>> moot. Where can I raise a defect?
>>>>
>>>> On Thursday, November 15, 2018 at 1:43:02 PM UTC-5, Randall Becker
>>>> wrote:
>>>>>
>>>>> Hi Mark,
>>>>>
>>>>> Yes, using a private key. This is a bitbucket.org site, which by my
>>>>> own company's policy prevents me from using a passphrase-less credential.
>>>>> The same key-pair is used elsewhere in other jobs in the same Jenkins
>>>>> without problems. The job is a multibranch job, not a simple pipeline. A
>>>>> simple pipeline (as tiny as I can get, as follows), works with this
>>>>> credential set:
>>>>>
>>>>> node('maven') {
>>>>> git branch: 'development', credentialsId: 'idalias', url:
>>>>> 'g...@bitbucket.org:MYURL.git'
>>>>> }
>>>>>
>>>>> So this is looking increasingly like an issue with Pipeline:
>>>>> Multibranch.
>>>>>
>>>>> Cheers,
>>>>> Randall
>>>>>
>>>>> On Thursday, November 15, 2018 at 12:38:43 PM UTC-5, Mark Waite wrote:
>>>>>>
>>>>>> I assume from your description that you're using a private key with a
>>>>>> passphrase as the credential in the Pipeline job definition.  I'm also
>>>>>> assuming it is a simple Pipeline job rather than a multibranch Pipeline.
>>>>>>
>>>>>> Does the same behavior happen if you use a private key which does not
>>>>>> have a passphrase?
>>>>>>
>>>>>> Does the same behavior happen if you use a multibranch Pipeline job
>>>>>> rather than a simple Pipeline job?
>>>>>>
>>>>>> Mark Waite
>>>>>>
>>>>>> On Thu, Nov 15, 2018 at 9:18 AM Randall Becker 
>>>>>> wrote:
>>>>>>
>>>>>>> The original post showed the entire list of refs. No issue requiring
>>>>>>> a timeout above 3 seconds actually. 10 minutes will make no difference.
>>

Re: Multibranch Pipeline Scan Hangs

[Mark Waite]

I created a multibranch Pipeline with bitbucket.org as the source using Git
as the branch source with a passphrase protected ed25519 private key.  It
scans and builds as expected.

I can't duplicate the problem that you're describing.  Before you spend the
time to submit a bug report, you may want to duplicate the bug in a
different environment, just in case there is something specific in your
environment that is different than my attempt to duplicate the problem.

Bug reports for the project are submitted to https://issues.jenkins-ci.org/
.

On Thu, Nov 15, 2018 at 3:11 PM Mark Waite 
wrote:

> I created a multibranch pipeline with bitbucket.org as the source using
> the Bitbucket Branch Source plugin.  That plugin prompted for a username /
> password rather than a private key.  It won't accept a private key.  I
> believe it uses REST APII calls to reduce the overhead of checking for new
> branches and for changes in the existing branches.  Since the REST API is
> based on https, it needs username / password rather than a private key.
>
> The Bitbucket Branch Source plugin provides additional capabilities
> because it is aware of Bitbucket, rather than being limited to those
> components which are generic git operations.
>
> Is there a reason you're not using the Bitbucket Branch Source plugin,
> rather than using the Git branch source?
>
> On Thu, Nov 15, 2018 at 12:24 PM Randall Becker 
> wrote:
>
>> There is also similar hang at fetch when the Jenkinsfile SCM is used. It
>> does appear that the credentials may not be supplied properly but there is
>> no indication that this is the case. I'm dropping back to Simple Pipelines
>> without SCM, sadly. This rather makes the whole point rather moot. Where
>> can I raise a defect?
>>
>> On Thursday, November 15, 2018 at 1:43:02 PM UTC-5, Randall Becker wrote:
>>>
>>> Hi Mark,
>>>
>>> Yes, using a private key. This is a bitbucket.org site, which by my own
>>> company's policy prevents me from using a passphrase-less credential. The
>>> same key-pair is used elsewhere in other jobs in the same Jenkins without
>>> problems. The job is a multibranch job, not a simple pipeline. A simple
>>> pipeline (as tiny as I can get, as follows), works with this credential set:
>>>
>>> node('maven') {
>>> git branch: 'development', credentialsId: 'idalias', url:
>>> 'g...@bitbucket.org:XXXXMYURL.git'
>>> }
>>>
>>> So this is looking increasingly like an issue with Pipeline: Multibranch.
>>>
>>> Cheers,
>>> Randall
>>>
>>> On Thursday, November 15, 2018 at 12:38:43 PM UTC-5, Mark Waite wrote:
>>>>
>>>> I assume from your description that you're using a private key with a
>>>> passphrase as the credential in the Pipeline job definition.  I'm also
>>>> assuming it is a simple Pipeline job rather than a multibranch Pipeline.
>>>>
>>>> Does the same behavior happen if you use a private key which does not
>>>> have a passphrase?
>>>>
>>>> Does the same behavior happen if you use a multibranch Pipeline job
>>>> rather than a simple Pipeline job?
>>>>
>>>> Mark Waite
>>>>
>>>> On Thu, Nov 15, 2018 at 9:18 AM Randall Becker 
>>>> wrote:
>>>>
>>>>> The original post showed the entire list of refs. No issue requiring a
>>>>> timeout above 3 seconds actually. 10 minutes will make no difference. When
>>>>> run from Jenkins from a shell command, the result comes back in seconds. I
>>>>> don't think this is a performance issue. It is seeming to be a problem in
>>>>> the plugin.
>>>>>
>>>>> On Thursday, November 15, 2018 at 11:07:20 AM UTC-5, Ivan Fernandez
>>>>> Calvo wrote:
>>>>>>
>>>>>> also, check the value of the TIMEOUT property, execute this code in
>>>>>> the Jenkins script console, the default value is 10 minutes, you can
>>>>>> increase it by setting the property in your command line
>>>>>>
>>>>>> System.getProperty(org.jenkinsci.plugins.gitclient.Git.class.getName()
>>>>>> + ".timeOut")
>>>>>>
>>>>>> If you have tons of tags on your repos try to not discover tags.
>>>>>>
>>>>>> El jueves, 15 de noviembre de 2018, 16:51:53 (UTC+1), Randall Becker
>>>>>> escribió:
>>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>

Re: Multibranch Pipeline Scan Hangs

[Mark Waite]

I created a multibranch pipeline with bitbucket.org as the source using the
Bitbucket Branch Source plugin.  That plugin prompted for a username /
password rather than a private key.  It won't accept a private key.  I
believe it uses REST APII calls to reduce the overhead of checking for new
branches and for changes in the existing branches.  Since the REST API is
based on https, it needs username / password rather than a private key.

The Bitbucket Branch Source plugin provides additional capabilities because
it is aware of Bitbucket, rather than being limited to those components
which are generic git operations.

Is there a reason you're not using the Bitbucket Branch Source plugin,
rather than using the Git branch source?

On Thu, Nov 15, 2018 at 12:24 PM Randall Becker 
wrote:

> There is also similar hang at fetch when the Jenkinsfile SCM is used. It
> does appear that the credentials may not be supplied properly but there is
> no indication that this is the case. I'm dropping back to Simple Pipelines
> without SCM, sadly. This rather makes the whole point rather moot. Where
> can I raise a defect?
>
> On Thursday, November 15, 2018 at 1:43:02 PM UTC-5, Randall Becker wrote:
>>
>> Hi Mark,
>>
>> Yes, using a private key. This is a bitbucket.org site, which by my own
>> company's policy prevents me from using a passphrase-less credential. The
>> same key-pair is used elsewhere in other jobs in the same Jenkins without
>> problems. The job is a multibranch job, not a simple pipeline. A simple
>> pipeline (as tiny as I can get, as follows), works with this credential set:
>>
>> node('maven') {
>> git branch: 'development', credentialsId: 'idalias', url:
>> 'g...@bitbucket.org:MYURL.git'
>> }
>>
>> So this is looking increasingly like an issue with Pipeline: Multibranch.
>>
>> Cheers,
>> Randall
>>
>> On Thursday, November 15, 2018 at 12:38:43 PM UTC-5, Mark Waite wrote:
>>>
>>> I assume from your description that you're using a private key with a
>>> passphrase as the credential in the Pipeline job definition.  I'm also
>>> assuming it is a simple Pipeline job rather than a multibranch Pipeline.
>>>
>>> Does the same behavior happen if you use a private key which does not
>>> have a passphrase?
>>>
>>> Does the same behavior happen if you use a multibranch Pipeline job
>>> rather than a simple Pipeline job?
>>>
>>> Mark Waite
>>>
>>> On Thu, Nov 15, 2018 at 9:18 AM Randall Becker 
>>> wrote:
>>>
>>>> The original post showed the entire list of refs. No issue requiring a
>>>> timeout above 3 seconds actually. 10 minutes will make no difference. When
>>>> run from Jenkins from a shell command, the result comes back in seconds. I
>>>> don't think this is a performance issue. It is seeming to be a problem in
>>>> the plugin.
>>>>
>>>> On Thursday, November 15, 2018 at 11:07:20 AM UTC-5, Ivan Fernandez
>>>> Calvo wrote:
>>>>>
>>>>> also, check the value of the TIMEOUT property, execute this code in
>>>>> the Jenkins script console, the default value is 10 minutes, you can
>>>>> increase it by setting the property in your command line
>>>>>
>>>>> System.getProperty(org.jenkinsci.plugins.gitclient.Git.class.getName()
>>>>> + ".timeOut")
>>>>>
>>>>> If you have tons of tags on your repos try to not discover tags.
>>>>>
>>>>> El jueves, 15 de noviembre de 2018, 16:51:53 (UTC+1), Randall Becker
>>>>> escribió:
>>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> I am trying to move over to Pipelines from Freestyle and am
>>>>>> experiencing a hang during the initial scan for branches at ls-remote in
>>>>>> the Multibranch Pipeline Scan. A few symptoms:
>>>>>>
>>>>>>
>>>>>>1. When using a freestyle project, with the same credentials and
>>>>>>URL, there is no issue.
>>>>>>2. When using ls-remote from the command line with the same
>>>>>>credentials and URL, there is no issue.
>>>>>>3. Git is available to Jenkins, but I tried providing a full path
>>>>>>- no change.
>>>>>>4. The project is minimal with no actual actions defined yet.
>>>>>>5. I am on Jenkins 2.138.2 and the latest plugins.
>>>>>>
>>>>&g

Re: Multibranch Pipeline Scan Hangs

[Mark Waite]

I assume from your description that you're using a private key with a
passphrase as the credential in the Pipeline job definition.  I'm also
assuming it is a simple Pipeline job rather than a multibranch Pipeline.

Does the same behavior happen if you use a private key which does not have
a passphrase?

Does the same behavior happen if you use a multibranch Pipeline job rather
than a simple Pipeline job?

Mark Waite

On Thu, Nov 15, 2018 at 9:18 AM Randall Becker 
wrote:

> The original post showed the entire list of refs. No issue requiring a
> timeout above 3 seconds actually. 10 minutes will make no difference. When
> run from Jenkins from a shell command, the result comes back in seconds. I
> don't think this is a performance issue. It is seeming to be a problem in
> the plugin.
>
> On Thursday, November 15, 2018 at 11:07:20 AM UTC-5, Ivan Fernandez Calvo
> wrote:
>>
>> also, check the value of the TIMEOUT property, execute this code in the
>> Jenkins script console, the default value is 10 minutes, you can increase
>> it by setting the property in your command line
>>
>> System.getProperty(org.jenkinsci.plugins.gitclient.Git.class.getName() +
>> ".timeOut")
>>
>> If you have tons of tags on your repos try to not discover tags.
>>
>> El jueves, 15 de noviembre de 2018, 16:51:53 (UTC+1), Randall Becker
>> escribió:
>>>
>>> Hi All,
>>>
>>> I am trying to move over to Pipelines from Freestyle and am experiencing
>>> a hang during the initial scan for branches at ls-remote in the Multibranch
>>> Pipeline Scan. A few symptoms:
>>>
>>>
>>>1. When using a freestyle project, with the same credentials and
>>>URL, there is no issue.
>>>2. When using ls-remote from the command line with the same
>>>credentials and URL, there is no issue.
>>>3. Git is available to Jenkins, but I tried providing a full path -
>>>no change.
>>>4. The project is minimal with no actual actions defined yet.
>>>5. I am on Jenkins 2.138.2 and the latest plugins.
>>>
>>> On interrupt, here is the stack trace:
>>>
>>> [Thu Nov 15 15:35:46 GMT 2018] Starting branch indexing...
>>>  > /usr/bin/git --version # timeout=10
>>> using GIT_SSH to set credentials Randall's Credentials
>>>  > /usr/bin/git ls-remote --symref 
>>> g...@bitbucket.org:X-my-private-url # timeout=10
>>>
>>> ERROR: [Thu Nov 15 15:40:45 GMT 2018] Could not update folder level actions 
>>> from source b9692b8b-7465-43bf-b59c-0103ba223697
>>> java.lang.InterruptedException
>>> at java.lang.Object.wait(Native Method)
>>> at java.lang.Object.wait(Object.java:502)
>>> at java.lang.UNIXProcess.waitFor(UNIXProcess.java:395)
>>> at hudson.Proc$LocalProc.join(Proc.java:324)
>>> at hudson.Proc.joinWithTimeout(Proc.java:170)
>>> at 
>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2012)
>>> at 
>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1735)
>>> at 
>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1640)
>>> at 
>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1631)
>>> at 
>>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteSymbolicReferences(CliGitAPIImpl.java:2893)
>>> at 
>>> jenkins.plugins.git.AbstractGitSCMSource.retrieveActions(AbstractGitSCMSource.java:1093)
>>> at jenkins.scm.api.SCMSource.fetchActions(SCMSource.java:765)
>>> at 
>>> jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:590)
>>> at 
>>> com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:277)
>>> at 
>>> com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165)
>>> at 
>>> jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1024)
>>> at hudson.model.ResourceController.execute(ResourceController.java:97)
>>> at hudson.model.Executor.run(Executor.java:429)
>>> [Thu Nov 15 15:40:45 GMT 2018] Finished branch indexing. Indexing took 4 
>>> min 59 sec
>>> Aborted
>>> Finished: ABORTED
>>>
>>> When running from the CLI:
>>>
>>> # GIT_SSH_COMMAND="ssh -i .ssh/id_rsa" /usr/bin/git ls-remote --symref

Re: how to find how a Jenkins instance is installed?

[Mark Waite]

I thought the question was trying to determine if the Jenkins installation
was done from apt, rpm, MSI, chocolatey, or using a war file.  Interesting
the different assumptions we make to a question.

Can the original questioner clarify what they were asking?

On Wed, Nov 14, 2018 at 7:33 PM Martin d'Anjou 
wrote:

> If you mean how do you test if an instance is ready (after a restart), you
> can use curl.
>
> httpCode=$(curl -s -w "%{http_code}" -X GET $JENKINS_URL)
> while [[  $httpCode != "200" ]]; do
> sleep 5
> httpCode=$(curl -s -w "%{http_code}" -X GET $JENKINS_URL)
> done
> echo "Jenkins is ready."
>
>
> On Wednesday, November 14, 2018 at 10:03:44 AM UTC-5, gotvi...@gmail.com
> wrote:
>>
>> Hello, how do I find out how a Jenkins instance has been installed?
>>
> --
> 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/70b0817f-aa60-42cc-bd83-713742c305aa%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/70b0817f-aa60-42cc-bd83-713742c305aa%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Re: Error fetching remote origin in Jenkins pipeline

[Mark Waite]

You'll need to provide more detail about the error.

The message "Error fetching remote origin" could be caused by many
different problems.

Some examples of the types of problems that might cause that message:

   - Credentials have changed to the gitlab server - git can't read from
   the remote server
   - Permissions have changed in the Jenkins workspace so that git can't
   write to the workspace
   - Remote repository no longer exists
   - Remote repository has been corrupted
   - Cached copy of the repository on the Jenkins master has been damaged
   - Host key of the gitlab server has change

Mark Waite

On Fri, Nov 9, 2018 at 3:30 PM Faad Sayaou  wrote:

> Everything was working fine until i added a new file to my
> gitlab repository. It seems jenkins is not keeping track of changes made to
> my repository and somehow inconsistent. I am getting the error* Error
> fetching remote origin in Jenkins pipeline *after adding this file. Any
> help on how to repair this ?
>
> --
> 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/53ac03b6-1925-4e33-b2aa-e9334f6db948%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/53ac03b6-1925-4e33-b2aa-e9334f6db948%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Re: I have setup Jenkins and am unable to run some my script, I now have to run some 'winds batch script'.I gave command mvn exec:java -Dexec.mainClass="test.automation.framework.Runner",but i am gett

[Mark Waite]

You're trying to run a Windows batch command on a Linux agent.  That won't
work.

If a Windows batch command is required, then you will need to use an agent
on a Windows computer.  Pipeline jobs usually control the agent they use
based on a label.  Freestyle and other jobs do the same.

Mark W

On Fri, Nov 9, 2018 at 7:51 AM  wrote:

> Commit message: "latest changes in schoolmanager class file"
>  > /opt/bitnami/git/bin/git rev-list --no-walk 
> 9ff69e6ef1d74435fa66ef3f7f540a0249e2085e # timeout=10
> [qa-automation] $ cmd /c call 
> /opt/bitnami/apache-tomcat/temp/jenkins7539709996486040665.bat
> FATAL: command execution failed
> java.io.IOException: error=2, No such file or directory
>   at java.lang.UNIXProcess.forkAndExec(Native Method)
>   at java.lang.UNIXProcess.(UNIXProcess.java:247)
>   at java.lang.ProcessImpl.start(ProcessImpl.java:134)
>   at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
> Caused: java.io.IOException: Cannot run program "cmd" (in directory 
> "/opt/bitnami/apps/jenkins/jenkins_home/workspace/qa-automation"): error=2, 
> No such file or directory
>   at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
>   at hudson.Proc$LocalProc.(Proc.java:249)
>   at hudson.Proc$LocalProc.(Proc.java:218)
>   at hudson.Launcher$LocalLauncher.launch(Launcher.java:929)
>   at hudson.Launcher$ProcStarter.start(Launcher.java:449)
>   at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:109)
>   at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
>   at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
>   at hudson.model.Build$BuildExecution.build(Build.java:206)
>   at hudson.model.Build$BuildExecution.doRun(Build.java:163)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
>   at hudson.model.Run.execute(Run.java:1794)
>   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
>   at hudson.model.ResourceController.execute(ResourceController.java:97)
>   at hudson.model.Executor.run(Executor.java:429)
> Build step 'Execute Windows batch command' marked build as failure
> Archiving artifacts
> Finished: 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/88164238-e30a-4d29-86a0-26ff32ac91cd%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/88164238-e30a-4d29-86a0-26ff32ac91cd%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Re: How to use environment variable in Jenkins Pipeline build?

[Mark Waite]

That's a good clarification.  I believe there is a known bug that the git
plugin does not expand variable references in some of the configuration
fields.

Use a multibranch Pipeline instead, then you can let the Pipeline script
expand the variable, and you won't have a confusing mix of changes in the
history of the job.

Mark Waite

On Thu, Nov 8, 2018 at 12:23 PM ZillaYT  wrote:

> Just to be clear, this is the text box in the job configuration page where
> I want to use an environment variable.
>
> [image: Screen Shot 2018-11-08 at 1.37.35 PM.png]
>
>
> On Thursday, November 8, 2018 at 2:19:06 PM UTC-5, ZillaYT wrote:
>>
>> It should work, but doesn't!
>>
>> I define my environment variable in Manage Jenkins->System Configuration,
>> Global Properties, Environment variables. I use the variable in other jobs
>> so I know the variable definition works!
>>
>> Thanks.
>>
>> On Thursday, November 8, 2018 at 12:45:18 PM UTC-5, Cuong Tran wrote:
>>>
>>> Where do you define your "environment variable"?
>>>
>>> It should work as ${BRANCH_TO_BUILD} if you define BRANCH_TO_BUILD under
>>> global environment variables, folder, inside your pipeline, etc.
>>>
>>>
>>> On Thursday, November 8, 2018 at 8:56:38 AM UTC-8, ZillaYT wrote:
>>>>
>>>> Someone suggested using ${env.branchToBuild}, so I tried env.branchToBuild,
>>>> $env.branchToBuild, ${env.branchToBuild}, and "${env.branchToBuild}"
>>>> all to NO avail.
>>>>
>>>> On Thursday, November 8, 2018 at 10:26:34 AM UTC-5, ZillaYT wrote:
>>>>>
>>>>> I have a Jenkins Pipeline job which uses "Pipeline script from SCM" as
>>>>> my pipeline. One of this block's parameters is "Branch to build" of 
>>>>> course.
>>>>> How can I used an environment variable for the text block? I tried, for
>>>>> example , $branchToBuild, ${branchToBuild} or "${branchToBuild}"  and
>>>>> it just takes those as literal values and does not extrapolate the string.
>>>>> I do have that variable defined and use it in other jobs.
>>>>>
>>>>> Is it just not possible to do this?
>>>>>
>>>> --
> 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/264ef2d4-3b6e-471c-8d98-40bc1e16496b%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/264ef2d4-3b6e-471c-8d98-40bc1e16496b%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Thanks!
Mark Waite

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

Re: Making the jenkins scm checkout smart

[Mark Waite]

Replies inline

On Tue, Oct 30, 2018 at 7:43 AM touseef  wrote:

> Hi ,
>
> I have a source code repository having multiple branches say branch1,
> branch2 and so on.
>
> Currently i have a jenkins jobs which builds the master or whatever i
> specify in job configuration.Now what i wish to achieve is if i commit my
> changes to branch 1 , my jenkins job should automatically context switch
> from master to branch1 and build that, and in the next step if i commit on
> branch2 it should  build branch 2.
>
> i am able to make rest calls via DSL script to get the branch names and
> then use job dsl  to create  the jobs  as the number of branches are
> present.
> However i don't want multiple jobs. What i am looking is having a single
> intelligent job to do the context switching between jobs.
>
>

Can you further explain why you want a "single intelligent job to do the
context switching"?

That is a technique that was used in the past with Jenkins freestyle jobs.
The technique makes it very hard to diagnose the locations of test
failures, or the place where a compilation failure happened, or the
differences from one job to the next.

If you're not using Pipeline jobs, then having a single job which builds
any of several branches is relatively easy (add the branch names to build),
though it will tend to confuse most users.

If you're using Pipeline jobs, you'll likely be much happier with a
multibranch pipeline so that each branch gets its own job and job history
and so that new jobs are created automatically for new branches and are
automatically destroyed for deleted branches.

Mark Waite


> Any idea or help will be appreciated.
>
> Thanks,
> Touseef
>
> --
> 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/3543d8da-3c80-4764-bc7c-092053f8c103%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/3543d8da-3c80-4764-bc7c-092053f8c103%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHHTJeWtSCsU5gGfCKf-qhH0OH21fGW1gDNteU%2BD4oLvw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem with Java 8 update 191?

[Mark Waite]

Those workspace names are not an indication of an incompatibility.  If
Jenkins needs to allocate a workspace and it detects that the default named
workspace is already in use, it will allocate a second workspace adjacent
to the first, with a digit appended to the workspace name.

Mark Waite

On Mon, Oct 29, 2018 at 11:28 PM James Fairweather <
james.fairweat...@blackbirdinteractive.com> wrote:

> Today I installed the version of Java from 8 build 181 to 8 build 191 on
> several build slaves.  After doing that, Jenkins started allocating a 2nd
> workspace on the some of the build agents.  For example, instead of running
> here:
>
> D:\projects\lion\main
>
> They were running here:
>
> D:\projects\lion\main@2
>
> Each build agent has been allocated a single executor.  We are running
> Jenkins 2.138.2.  I rolled the version of Java on the non-working agents
> back to Update 181 and the problem went away.
>
> Does anyone know if Java 8 Update 191 has some kind of incompatibility
> problem with Jenkins?
>
> --
> 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/CALg80NUJuzJ8nsMkTqwewuLn4UFvATinP0rvA%3DcMv_n-_WmPfg%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CALg80NUJuzJ8nsMkTqwewuLn4UFvATinP0rvA%3DcMv_n-_WmPfg%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEJaL1wyweKHmt-11-R2BbZ4ujy45hD1T-r6oc6uhz6BQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Connecting Jenkins to GitHub

[Mark Waite]

If Jenkins is running under your user id and the GitHub repository URL is
using SSH and you're using command line git as the git implementation, then
command line git fallback to use your default ssh private key.  That's a
behavior of command line git more than a behavior of Jenkins.

If Jenkins is running under your user id and the GitHub repository https
repository credentials have been permanently stored with git credentials,
then command line git will use those credentials.

If Jenkins is running under another user id or the GitHub repository URL is
using https without stored credentials or you're using JGit, then a
credential will need to be provided.

It is usually best to provide those credentials and not rely on command
line git defaults.

Mark Waite

On Mon, Oct 29, 2018 at 1:56 PM HB  wrote:

> Thank you.  After installing the GitHub integration plugin and watching
> the video, I was able to create a project just as in the video.
>
> My GitHub repository contains only the README.md file as well, however the
> difference is that my repo is private.  The item I create to my private
> repo on GitHub is not requiring that I add any credentials.  Despite not
> creating any credentials after clicking the git radio button under 'Source
> Code Management', I can just save the item successfully.  I can also click
> on the GitHub link within the project and it takes me right to the repo in
> GitHub.
>
> Does this sound correct?  I feel like it should require defining
> credentials to successfully connect to GitHub.  Or is it that I am being
> successfully connected via the public key that I put in place on the GitHub
> side?  Or is it possibly a cookie that is allowing the connection?  Is that
> something I can verify some how?
>
> Thanks,
>
> HB
>
> On Sunday, October 28, 2018 at 8:32:54 PM UTC-7, sagar utekar wrote:
>>
>> Hi,
>>
>> Search for a GitHub integration plugin.
>>
>> Here is a YouTube video link you can refer -
>> https://youtu.be/Z3S2gMBUkBo
>>
>> Thank you.
>>
>> On Mon, 29 Oct 2018, 08:55 HB,  wrote:
>>
>>> Thank you for the reply.  I am not seeing 'gith' plugin, is that short
>>> for a plugin?  Here are the plugins that I have installed referring to git
>>> and ssh:
>>>
>>> Git client plugin
>>> 2.7.3
>>> Git plugin
>>> 3.9.1
>>> GIT server Plugin
>>> 1.7
>>> GitHub API Plugin
>>> 1.92
>>> GitHub Branch Source Plugin
>>> 2.4.1
>>> GitHub plugin
>>> 1.29.3
>>>
>>> SSH Credentials Plugin
>>> 1.14
>>> SSH Slaves plugin
>>> 1.28.1
>>>
>>> Am I missing plugins that you are referring to?  Thanks again, any
>>> guidance is greatly appreciated..
>>>
>>> HB
>>>
>>> On Sunday, October 28, 2018 at 7:07:08 PM UTC-7, Robert Rajendra wrote:
>>>>
>>>> To integrate Jenkins with github. You need to install gith , github
>>>> plugins with ssh plugin you can read the docs regarding these and get the
>>>> work done
>>>>
>>>> On Mon, 29 Oct 2018, 3:06 am HB,  wrote:
>>>>
>>>>> All,
>>>>>
>>>>> I am completely new to Jenkins but am tasked with getting a working
>>>>> environment up and running.
>>>>>
>>>>> Everything appears to running well as follows:
>>>>>
>>>>> RHEL 7.5
>>>>> Jenkins ver 2.148
>>>>>
>>>>> Installed using the below yum repo:
>>>>> [jenkins]
>>>>> name=Jenkins
>>>>> baseurl=http://pkg.jenkins.io/redhat
>>>>> gpgcheck=1
>>>>>
>>>>> I have it configured to use Active Directory for user authentication
>>>>> and roles.
>>>>>
>>>>> My questions revolve around getting Jenkins connected to GitHub.  I am
>>>>> following these steps:
>>>>>
>>>>> https://gist.github.com/misterbrownlee/3708738
>>>>>
>>>>> I have created a 'utility user' (say git-jenkins) in GitHub that will
>>>>> ideally be the user that Jenkins uses to connect to GitHub.  I also have
>>>>> created a key pair for the connection.  Since Jenkins runs as user
>>>>> 'jenkins' on the server, I created the key pair as this user and imported
>>>>> the public key to the 'git-jenkins' utility user in GitHub.
>>>>>
>>>>> I also set:
>>>>>
>>>>> Global Config user.name Value
>>>

Re: Windows Agent As a Service

[Mark Waite]

The deprecation of Java Web Start doesn't deprecate the protocols that a
Jenkins agent can use to connect to the Jenkins server.  JNLP works just
fine with Java 11 to connect an agent.

The convenience of clicking the "Web Start" button on the UI won't work
with Java 11, but the command line provided in the agent start page
continues to work.

Mark Waite

On Mon, Oct 15, 2018 at 2:18 PM Mark Bidewell  wrote:

> With Java Web Start deprecated and slated for removal, what is the
> canonical way to create a Windows Service agent?
>
> 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/439b2186-1f70-46bd-b0f8-c54512eb428b%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/439b2186-1f70-46bd-b0f8-c54512eb428b%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEF%2BVvGu9TAm8P2YPcYgOQN899r0DfS%3DfXJj2eRdb%2BMLg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is there a way to get a tool's path value in pipeline?

[Mark Waite]

Since the git tool may be entirely internal to the Jenkins java code (as
with JGit), I'm not sure that will be as portable as you want it to be.

I don't know the answer to your specific question about the data available
related to a specific tool.

Mark Waite

On Fri, Oct 12, 2018 at 2:32 PM t3knoid  wrote:

> Typically I use checkout to checkout code from git. But sometimes I need
> to shell out and execute git. I can hardcode the path in my shell script or
> add the git directory in the PATH variable. I was thinking if there was a
> way to avoid that and use the configured git tool within Jenkins and pass
> that value in my shell script. So in essence, run a command similar to this:
>
> bat returnStdout: true, script: '${installed_git}  rev-list HEAD --count'
>
> Where ${installed_git} contains the value of the path of the git tool
> configured in Jenkins.
>
> --
> 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/49ae7954-620f-44bf-b384-bef9bccb9e27%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/49ae7954-620f-44bf-b384-bef9bccb9e27%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGsM8XBULUXPm4G22OJyYB%3D19UKQfeKZGs3djJPzXEH4A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: github teamfolder plugin

[Mark Waite]

GitHub Branch Source replaces it.  It is obsolete because all the
functionality it provided is now available in the GitHub Branch Source
plugin.

On Thu, Oct 4, 2018 at 3:25 PM David Karlsen  wrote:

> https://plugins.jenkins.io/github-organization-folder
> says it is obsolete.
> what replaces it? why is it obsolete?
>
> --
> --
> David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
>
> --
> 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/CAGO7Ob0YRJ-McNh72caFEyCMMpFVDOE5WKE_FW0u99cvPmNKnA%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/CAO49JtFXAkN1oKvXdbZ97MNrZFE9VGT9YnNKbKVnU_Hs0OfxUw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins pipelines

[Mark Waite]

Here are some possible resources that I found:

   - Several very good Pipeline tutorials are available on jenkins.io
   <https://jenkins.io/doc/tutorials/> along with the guided tour
   <https://jenkins.io/doc/pipeline/tour/getting-started/>.
   - Edureka offers their Jenkins video tutorials
   
<https://www.youtube.com/watch?v=Lxd6JMMxuwo=PL9ooVrP1hQOGM6eCsjnfAousUSvpqD8dW>
   on youtube.
   - Tech Primers offers their Jenkins video tutorials
   
<https://www.youtube.com/watch?v=BfJvxGs-HxQ=PLTyWtrsGknYc0bNLa-m0EeHApOizK4mS9>
   on youtube.
   - ProgrammingKnowledge offers their Jenkins video tutorials
   
<https://www.youtube.com/watch?v=yz3tyeA3Fe0=PLS1QulWo1RIbY8xXPqz6ad_sNHkIP3IXI>
   on youtube.
   - There is a list of "5 Best Jenkins Tutorials
   <https://digitaldefynd.com/best-jenkins-tutorial-training-course/>"
   which you might consider as well (note that some of them are not free).
   - If you register a free account with CloudBees (at
   https://go.cloudbees.com/training), you can also take the Jenkins
   Pipeline Fundamentals course for free ("View Online Courses").


Mark Waite

On Thu, Oct 4, 2018 at 5:41 AM  wrote:

> I want to learn how to write jenkins pipeline so Please suggest me a
> course or from where i can start
>
>
> Please HELP!
>
> and Please suggest what i need to do to learn  writing jenkins 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/bc2d2abd-01ca-44ac-9a62-b0b7a0617aa6%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/bc2d2abd-01ca-44ac-9a62-b0b7a0617aa6%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtH7ztrsFV5h5a9sWUj9DEE_eGwgyG6UsGt-XVL85axO4Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Failure to build Jenkins from source

[Mark Waite]

Looks like you're using Apache Maven 3.5.2 while the instructions at
https://github.com/jenkinsci/jenkins/blob/master/CONTRIBUTING.md say that
you need at least Apache Maven 3.5.3.  The failure message tells you what
you'll need to do.

You need to download and install Apache Maven 3.5.4 from
https://maven.apache.org/download.cgi

Mark Waite

On Wed, Oct 3, 2018 at 1:39 PM Gerry Storm  wrote:

> I followed instructions in
> https://wiki.jenkins.io/display/JENKINS/Building+Jenkins to build Jenkins
> on my Ubuntu box.
>
> The build failed with the following error:
>
> Adding failure due to exception
> org.apache.maven.enforcer.rule.api.EnforcerRuleException: 3.5.4+ required
> to use Incrementals.
>
> See also attached file for details.
>
> --
> G
>
> --
> 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/bc6b1ec2-28ac-4d65-ac7f-b179483423cc%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/bc6b1ec2-28ac-4d65-ac7f-b179483423cc%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFGMH3EP5uPsyLoXZYiwbzjrC2bAfnSVsq%2BCNB1KDOi%2BQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins pipeline

[Mark Waite]

You might also consider the detailed Jenkins and npm tutorial at
https://jenkins.io/doc/tutorials/build-a-node-js-and-react-app-with-npm/

Mark Waite

On Wed, Oct 3, 2018 at 6:52 AM Jan Monterrubio 
wrote:

> Secrets:
>
> https://support.cloudbees.com/hc/en-us/articles/203802500-Injecting-Secrets-into-Jenkins-Build-Jobs?mobile_site=true
>
> I believe they’d be environment variables.
>
> Compiling: if you’re using maven just run mvn clean package or you could
> have mvn deploy push the artifact to some repository and your staging
> machine would just pull from that repo.
>
> For pipeline/git the following page might help:
>
> https://jenkins.io/doc/tutorials/build-a-java-app-with-maven/#fork-sample-repository
>
>
> On Wed, Oct 3, 2018 at 01:38  wrote:
>
>> # i don't know much about Jenkins pipeline but this is my first time and
>> here is what I did
>>
>> //** pipeline to get the code from git branches and deploy to the staging
>> or production server **//
>>
>> node {
>>def mvnHome
>>stage('Preparation') { // for display purposes
>>   // Get some code from a GitHub repository
>>   git 'https://github.com/jglick/simple-maven-project-with-tests.git'
>>   // Get the Maven tool.
>>   // ** NOTE: This 'M3' Maven tool must be configured
>>   // **   in the global configuration.
>>}
>>stage('Execute commannds') {
>>   //** Here you will aff the additional commands line npm
>>
>>   }
>>}
>>stage('deploy staging') {
>>   ssh $user@IP 'cd $location && git status && git pll origin staging
>> '\
>>
>>}
>> }
>>
>> if this is right Please guide me that how do I add the staging and
>> production branches accordingly and if i want to compile the code on the
>> way how do i do that . + how do i add secret variables in the jenkins that
>> i can use in the pipeline script
>>
>>
>>
>>
>>
>> --
>> 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/74eaf638-f1ba-4026-a67b-a2479da965e0%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/74eaf638-f1ba-4026-a67b-a2479da965e0%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CADgiF9%2BY06e4jjiCtDXo5RUK6htv%3DCQA6usCB%2BYycbX_1kPxuQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CADgiF9%2BY06e4jjiCtDXo5RUK6htv%3DCQA6usCB%2BYycbX_1kPxuQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHNAjDxhkMz1qaTB9N%3Drk21HFufJg6pr0RBJz_3ktVdmw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multiple Github repositories in a build

[Mark Waite]

If you're using a Jenkins Pipeline, you can checkout multiple repositories
so long as each repository is placed into its own directory in the
workspace.  You define the checkout, including the repository URL, the
credentials, and the branch.

If you're not using a Jenkins Pipeline, you should not use multiple
repositories.  Yes, there are techniques like the multiple SCM plugin that
will allow some multiple repository scenarios, but none of them work as
well as Pipeline.

Refer to
https://github.com/MarkEWaite/jenkins-bugs/blob/526b36de2203f65ada40b9a606c7cba1cddcfa98/Jenkinsfile#L37
for
one example.  In that example, a checkout of a non-master branch is
followed by a ws() { } block which then performs a checkout of the master
branch inside the new workspace created by the 'ws() { } block.

Mark Waite

On Mon, Oct 1, 2018 at 5:49 PM  wrote:

> I have some builds that require multiple github repos.  One contains build
> scripts on master branch.   ANother contains code on a different branch.
>
> I noticed the source code management settings in Jenkins there is a way to
> add another repository but it only allows me to specify one branch.
>
> How can I add another repository to my build project?
>
>
>
> thanks in advance.
>
> --
> 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/7da67a84-b965-4a03-b6f0-a85f4d66543e%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/7da67a84-b965-4a03-b6f0-a85f4d66543e%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtG-J8nf2HGhXDYFTpS485La%3D2HzMqr47kEjauKzJmdKiA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Testing failed after migrating to 2.121 LTS

[Mark Waite]

You'll need to provide significantly more details before anyone will be
able to provide meaningful help.

Some of the questions that arose when I saw your description:

   - Is that failure in a specific job or in every job?
   - What are the characteristics of that job (if a specific job)?
   - Do those tests fail when executed from the command line?
   - Do those tests fail when executed from inside a Docker image defined
   to build and execute the tests?
   - Since I've never seen an "org.testing.Assert" library, I assume there
   is either a typo in your stack trace or you're using a special library.  Is
   there a typo or are you using a special library?
   - Can you duplicate the failure outside Jenkins?
   - What JDK are you running in the failing environment?
   - What JDK was running in the environment where it worked?
   - Is this specific to a certain platform (Windows, Linux, FreeBSD,
   zLinux, etc.)

By posting minimal information and then repeatedly asking for a status
update, you're not showing any indication that you've investigated the
issue more deeply yourself, nor that you're willing to spend energy to
investigate more deeply.

Persuade the people in the mailing list that you've investigated further by
including detailed descriptions of the experiments you've attempted and the
results of those experiments.  Describing your investigation will help you
and will probably help others who encounter similar problems in the future.

Mark Waite

On Mon, Sep 24, 2018 at 9:52 AM Pranav Kv  wrote:

> Any updates?
>
> Thanks
>
> On Mon, 24 Sep 2018, 6:05 am Pranav Kv,  wrote:
>
>> Anyone can help on this?
>>
>> On Thu, 20 Sep 2018, 8:34 pm Pranav Kv,  wrote:
>>
>>> Still failing validation error in jenkins LTS 2.121..but no issue with
>>> 1.644
>>>
>>> Java.lang.AssertionError: file abcd.xml validation rule not trigger,
>>> validation error found:[] expected [[abcd.xml]] but found [[]]
>>>
>>> org.testing.Assert.fail(Aasert.java94))
>>> org.testing.Assert.failNotEquals(Asser. Java:494)
>>> org.testing.Assert.assertEqual(Assert.java:808)
>>>
>>> --
>>> 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/8a6efbb7-2868-4885-b4c7-ef9294ea4dde%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/CAHwQEkKWUpubxR3Hj_yZL-4rs90s%2BsgNL7Bcij5YqhMD3_-yTA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAHwQEkKWUpubxR3Hj_yZL-4rs90s%2BsgNL7Bcij5YqhMD3_-yTA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFSrW4Wqd7OUPjPNzyMXSYoE-qjpcC9gYnxDqiGC4a4Ng%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: structs v1.7 is missing. To fix, install v1.7 or later.

[Mark Waite]

Steve,

Please don't hijack the questions of others.  I think it is unfair to do
that to the original requester and to those responding to that question.

I'm sorry that your problem is not yet resolved.  My previous attempts to
resolve your issue with brief answers have failed.  The problem is still
there for you.  I can't duplicate your problem.  It seemed to me when I
read the e-mail you sent to me directly yesterday that you needed a much
more detailed response that will show step by step my guesses of how to
resolve the problem you're seeing.

I arrived home last night after midnight after a week of business travel.
I've been working 12 hour days for a month or more preparing for last
week's conference.  I was traveling when I saw your request for help in my
personal e-mail less than 24 hours ago.  I was exhausted when I arrived
home after midnight and didn't give you an answer.  Unfortunately, after a
week of travel, I'm hesitant to give you a significant amount of my family
time.

While you are welcome to send me e-mail directly as you did, I think it is
unreasonable to expect a response on a weekend and less than 24 hours after
you sent the initial request.  I have already offered all the short answers
that I thought would resolve your issue.  They didn't resolve it.  I
believed last night that the next answer will need to be much longer and
much more detailed since the short answers have not solved the problem.

If you are demanding a yes/no answer, then my answer is "no", I won't help
you.  Your expectations of help seem to be that I'll provide detailed
answers rapidly.  I can't commit to do that.

If you're willing to receive answers on my timeline, then 3-4 days from now
I may be able to provide the detailed answer that I think will be required.

Mark Waite

On Sun, Sep 23, 2018 at 1:33 PM Steve Burrus  wrote:

> Mark Waite do yoiu NOT ch oose to help me any further with my continuing
> problem with always get the login page after I have successfully activated
> Jenkins? Just go ahead and tell me that you don't WANT TO help me any more
> and I will seek other sources of help/assistance. Please respond to me soon
> as I really want to finally resolve this.
>
> On Sun, Sep 23, 2018 at 2:00 PM Mark Waite 
> wrote:
>
>> When I downloaded structs-1.7.hpi from the Jenkins artifact repository,
>> it was 50 KB, not 38 KB.
>>
>> Are you using the Plugin Manager to download the plugins, or trying to do
>> the work of downloading the plugins yourself?
>>
>> The Jenkins user interface is the best choice to download plugins, since
>> it will download the requested plugin and all its dependencies.
>>
>> Mark Waite
>>
>> On Sun, Sep 23, 2018 at 10:59 AM Baptiste Mathus  wrote:
>>
>>> Did you check the structs.jpi is not corrupted?
>>>
>>> Cf. https://updates.jenkins.io/download/plugins/structs/ where you'll
>>> see the expected SHA1.
>>> What is the sha1 of your structs.jpi file? Can you open it as a zip file?
>>>
>>> Le dim. 23 sept. 2018 à 15:23, DEEPAK VERMA 
>>> a écrit :
>>>
>>>> i am getting this error.
>>>> structs v1.7 is missing. To fix, install v1.7 or later.
>>>>
>>>> Although I placed the struts and performance plugin at designated
>>>> folder but still getting this error.
>>>>
>>>> P.S. What ever suggestion come, please write all commands and step wise
>>>> process to resolve this as I am very new in Jenkins.
>>>>
>>>>
>>>> --
>>>> 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/6d98d6fa-6106-497a-a888-432f9b7d8d94%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-users/6d98d6fa-6106-497a-a888-432f9b7d8d94%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS4r24HNy31azoKTYmheqVVnBnY%2BUeJdLaE8%2BGF-cd46Pw%40mail.gmail.com
>>> <

Re: structs v1.7 is missing. To fix, install v1.7 or later.

[Mark Waite]

When I downloaded structs-1.7.hpi from the Jenkins artifact repository, it
was 50 KB, not 38 KB.

Are you using the Plugin Manager to download the plugins, or trying to do
the work of downloading the plugins yourself?

The Jenkins user interface is the best choice to download plugins, since it
will download the requested plugin and all its dependencies.

Mark Waite

On Sun, Sep 23, 2018 at 10:59 AM Baptiste Mathus  wrote:

> Did you check the structs.jpi is not corrupted?
>
> Cf. https://updates.jenkins.io/download/plugins/structs/ where you'll see
> the expected SHA1.
> What is the sha1 of your structs.jpi file? Can you open it as a zip file?
>
> Le dim. 23 sept. 2018 à 15:23, DEEPAK VERMA 
> a écrit :
>
>> i am getting this error.
>> structs v1.7 is missing. To fix, install v1.7 or later.
>>
>> Although I placed the struts and performance plugin at designated folder
>> but still getting this error.
>>
>> P.S. What ever suggestion come, please write all commands and step wise
>> process to resolve this as I am very new in Jenkins.
>>
>>
>> --
>> 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/6d98d6fa-6106-497a-a888-432f9b7d8d94%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/6d98d6fa-6106-497a-a888-432f9b7d8d94%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS4r24HNy31azoKTYmheqVVnBnY%2BUeJdLaE8%2BGF-cd46Pw%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS4r24HNy31azoKTYmheqVVnBnY%2BUeJdLaE8%2BGF-cd46Pw%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtH5r3CtdVv9695w4AcAQDxJJwcfe-CuGpoXvdQhUkxqkw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to check plugin version for a specific jenkins version

[Mark Waite]

The Jenkins-Version field embedded in the plugin manifest file is the
minimum Jenkins version supported, not the maximum.  Jenkins works very
hard to allow older plugins to continue operating in newer releases.

Mark Waite

On Thu, Sep 20, 2018 at 9:09 PM Narahari 'n' Savitha 
wrote:

> Thank you folks in advance for your time and attention
>
> Here is the scenario.
>
> I have Jenkins LTS 2.122 version and I have plugins for that installed.
>
> Now the Jenkins 2.138 is released and I want to upgrade.
>
> How do I check the version for the plugin that  works for 2.138 or below ?
> Apart from downloading plugin, unwrapping it and look at the Jenkins
> version field, is there any other way ?
>
> This is doable but it is very laborious and I have to go from what ver of
> plugin I have and go up one level check and keep going up the version list.
>
> I am trying to pick minds of smart people here please.
>
> -N
>
> --
> 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/3507d3d8-4478-4024-952d-4c49f7b587f8%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/3507d3d8-4478-4024-952d-4c49f7b587f8%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEXU3GiUM-i8yDB15H09G%3D_dQij862eXMjYA7XWjFsG3Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Blue ocean plugin supported version

[Mark Waite]

Blue ocean runs well on that version.

Mark Waite

On Wed, Sep 19, 2018, 10:20 PM Pranav Kv  wrote:

> Recently we migrated jenkins to latest LTS
> Version of jenkins(2.121).But now one of our customer wants to install
> jenkins blue ocean plugin. But as per my understand blue ocean plugin
> support only jenkins 2.7 or higher version. Please let me know jenkins
> 2.121LTS can support blue ocean 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/38c81e27-ec3b-4e3e-9923-6cf663ee967d%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/CAO49JtGcSpnr4ibqybmGNP0qyVbOpJeEY0xaiuN%2B1ZYy%2B_OuGw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Relationship between GitHub credentials and Jenkins Service account (running as Windows Service)

[Mark Waite]

The message "Host key verification failed" is only reported by git when it
is using a private key for authentication.  A personal access token is a
type of username/password, not a type of private key.

You may want to double check that the GitHub URL that you are using is an
https URL, not an ssh URL.  The https URL's use personal access tokens.
The ssh URL's (like ssh://g...@github.com/MarkEWaite/git-plugin.git and
g...@github.com:MarkEWaite/git-plugin.git) use private keys.

Mark Waite

On Thu, Sep 13, 2018 at 9:07 AM Christopher List  wrote:

> We are running Jenkins as a windows service on win2012 machine, and it's
> working fine.
>
> The problem we have is that we're trying to change the service account
> that it is running under.
> The old and new service accounts are both local admins on the machine.
>
> When we change the service account, everything seems to run fine, but our
> connection to GitHub using a Personal Access token stored in the global
> jenkins credentials stops working with the classic error:
>
> stderr: Host key verification failed.
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>
>
>
> I've re-entered the credentials into Jenkins (thinking perhaps they are
> secured by the service account) and they still don't work.
> As soon as I change the jenkins service back to the old service account,
> the pull from GitHub works fine.
>
> Do I need to grant the new account access to something? Is there something
> I need to configure in Jenkins for the new service account? (note that I
> didn't do the original setup of jenkins on this server, I've inherited it)
>
> Thanks,
> Chris
>
> --
> 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/ca29e9ef-fa81-4040-9ea2-49f1a9d36417%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/ca29e9ef-fa81-4040-9ea2-49f1a9d36417%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFKeZeRX9yZ78a1HgKZ75rNK0k29UHVy_Fq3oYy7rvGLA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Still Login Problem.

[Mark Waite]

I infer from that paragraph that you started Jenkins from a command prompt
window.  If so, then you can define the value for JENKINS_HOME before you
run the "java -jar jenkins.jar" command.  Jenkins will use the value you
defined for JENKINS_HOME.

Jenkins starts initially as "secure by default".  The initial administrator
password is written to the command prompt window during startup and is also
written to the JENKINS_HOME directory as the file
secrets\initialAdminPassword.

Once you've used that initial admin password to login, it will prompt you
to create a new user and assign a password to that user.

The post-installation setup wizard
<https://jenkins.io/doc/book/installing/#setup-wizard> is the guide for
that process.

Mark Waite

On Sat, Sep 8, 2018 at 1:42 PM Steve Burrus  wrote:

>
>
> *I’m sorry but I haven’t evr even gotten to capture the "Manage Jenkins"
> -> "System Information" page. No when I seemed to activate Jenkins in my
> command prompt I then went, in my web browser, to the localhost but then I
> always get the login page which I really DON’T WANT. *
>
>
>
> *Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows 10*
>
>
>
> *From: *
>
>
> *Mark Waite Sent: Saturday, September 8, 2018
> 2:35 PMTo: jenkinsci-users@googlegroups.com
> Subject: Re: Still Login Problem.*
>
>
>
> *When you've reset and done a clean setup, you may want to capture the
> "Manage Jenkins" -> "System Information" page to record the value of the
> variable "JENKINS_HOME".*
>
>
>
> *JENKINS_HOME is the directory which contains the "config.xml" file that I
> described earlier.  Inside %JENKINS_HOME%\config.xml you'll find the
> '' XML tag.*
>
>
>
> *Mark Waite*
>
>
>
> *On Sat, Sep 8, 2018 at 1:21 PM Steve Burrus  > wrote:*
>
> *Ya I have tried dpoing th at maybe 2-3 times before "start over with a
> clean setup." to no avail BUT I will try doing that yet again [if that
> helps I don't know]. But no I didn't have any jobs on it.*
>
> *On Sat, Sep 8, 2018 at 1:31 PM Slide  > wrote:*
>
> *Do you have jobs that you want to keep the data and configuration for, or
> is the setup pretty fresh? If it's pretty fresh and you are ok with
> starting over, you could delete the directory that contains that config.xml
> file (JENKINS_HOME) and start over with a clean setup.*
>
>
>
>
>
>
>
> *-- 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/CABinwmU_NPraYrfp%2B5nP5mrHBFPsk126nAqyEa6OE42Qyp3FXA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CABinwmU_NPraYrfp%2B5nP5mrHBFPsk126nAqyEa6OE42Qyp3FXA%40mail.gmail.com?utm_medium=email_source=footer>.For
> more options, visit https://groups.google.com/d/optout
> <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/CAO49JtFy%2BV-yA86Ja0pFmuAH0dMeP9fxZGZ_Ta1xKJPFYRSjbA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFy%2BV-yA86Ja0pFmuAH0dMeP9fxZGZ_Ta1xKJPFYRSjbA%40mail.gmail.com?utm_medium=email_source=footer>.For
> more options, visit https://groups.google.com/d/optout
> <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/5b942607.1c69fb81.65ae7.5c27%40mx.google.com
> <https://groups.google.com/d/msgid/jenkinsci-users/5b942607.1c69fb81.65ae7.5c27%40mx.google.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGmmrA7pt8mO5%3Dwb%2BaQHayH3g9di1ZWd-eBNAtjnbKzaQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Still Login Problem.

[Mark Waite]

When you've reset and done a clean setup, you may want to capture the
"Manage Jenkins" -> "System Information" page to record the value of the
variable "JENKINS_HOME".

JENKINS_HOME is the directory which contains the "config.xml" file that I
described earlier.  Inside %JENKINS_HOME%\config.xml you'll find the
'' XML tag.

Mark Waite

On Sat, Sep 8, 2018 at 1:21 PM Steve Burrus  wrote:

>
>
> *Ya I have tried dpoing th at maybe 2-3 times before "start over with a
> clean setup." to no avail BUT I will try doing that yet again [if that
> helps I don't know]. But no I didn't have any jobs on it.*
>
> *On Sat, Sep 8, 2018 at 1:31 PM Slide  > wrote:*
>
>> *Do you have jobs that you want to keep the data and configuration for,
>> or is the setup pretty fresh? If it's pretty fresh and you are ok with
>> starting over, you could delete the directory that contains that config.xml
>> file (JENKINS_HOME) and start over with a clean setup.*
>>
>>
>> --
> 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/CABinwmU_NPraYrfp%2B5nP5mrHBFPsk126nAqyEa6OE42Qyp3FXA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CABinwmU_NPraYrfp%2B5nP5mrHBFPsk126nAqyEa6OE42Qyp3FXA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFy%2BV-yA86Ja0pFmuAH0dMeP9fxZGZ_Ta1xKJPFYRSjbA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Need Login Help

[Mark Waite]

Your search tool may be refusing to index the location where the file is
stored.  Try a different search technique.

Try the following from an Administrator Windows Command Prompt:

C:\> FINDSTR /L useSecurity "%ProgramFiles(x86)%"

If that doesn't work, you could try installing some other program that will
search for strings or file names on your disc.

If you have multiple drives (C:, D:, etc.), you might check to see if
Jenkins was installed on one of the other drives.

The
https://www.howtogeek.com/99406/how-to-search-for-text-inside-of-any-file-using-windows-search/
page
suggests that Windows search might be choosing to not index the
xml configuration files.  If so, then it gives hints that may help you
change that setting.

Mark Waite

On Fri, Sep 7, 2018 at 9:16 AM Steve Burrus  wrote:

> *Mark I absolutely CANNOT FIND the config.xml file after looking all over
> for it. Any solutions?*
>
>
> On Thu, Sep 6, 2018 at 9:55 PM Mark Waite 
> wrote:
>
>> The file jenkins.exe.config controls the way Windows executes the program
>> "jenkins.exe".  It does not store the global Jenkins configuration.
>>
>> The global Jenkins configuration (including the  setting) is
>> stored in a file named "config.xml".  The file that needs to be modified is
>> not named "jenkins.exe.config", it is named "config.xml".
>>
>> If you search your file system (Windows search, or with a find command)
>> for a file which contains the text "true" and is
>> named "config.xml", that is the file.  A file of any other name won't do.
>> Adding the text to any other file won't do.
>>
>> All the best!
>> Mark Waite
>>
>>
>> On Thu, Sep 6, 2018 at 7:59 PM Steve Burrus  wrote:
>>
>>> Mark here is what I have in my "C:\MyJenkins\jenkins.exe.config"
>>> file.Here is what I have inside the file :
>>> 
>>>   
>>> 
>>>   
>>>   
>>> 
>>> 
>>>   
>>> 
>>> Now should I put that  line in THIS file, and
>>> if so where?
>>>
>>>
>>> On Thu, Sep 6, 2018 at 8:09 PM Mark Waite 
>>> wrote:
>>>
>>>> It depends on how you are running Jenkins.
>>>>
>>>> If you are running Jenkins from a command line using the war file, like:
>>>>
>>>> C:\Users\Mark\my-jenkins> java -jar jenkins.war
>>>>
>>>> then the Jenkins HOME directory is placed in the ".jenkins"
>>>> subdirectory of your home directory.  In my case, that means I have:
>>>>
>>>> C:\Users\Mark\.jenkins\config.xml
>>>>
>>>> that contains the line 'true'
>>>>
>>>> If you are running Jenkins as configured with the MSI installer, then
>>>> the file is:
>>>>
>>>> C:\Program Files (x86)\Jenkins\config.xml
>>>>
>>>> If you've modified your installation by setting a value for
>>>> JENKINS_HOME before starting Jenkins, then that is where it was placed.
>>>>
>>>> If none of those match your installation, please describe in more
>>>> detail how you have installed Jenkins on your Windows 10 machine.
>>>>
>>>> Mark Waite
>>>>
>>>> On Thu, Sep 6, 2018 at 5:03 PM Steve Burrus 
>>>> wrote:
>>>>
>>>>> *I'm sorry but I can't find that config.xml file in my Windows 10
>>>>> enterprise system. How exactly can I get to it?  I have ON the setting
>>>>> "Show Hidden Files and Folders".  *
>>>>>
>>>>>
>>>>>
>>>>> *On Thu, Sep 6, 2018 at 4:55 PM Mark Waite >>>> > wrote:*
>>>>>
>>>>>>
>>>>>> *https://stackoverflow.com/questions/6988849/how-to-reset-jenkins-security-settings-from-the-command-line
>>>>>> <https://stackoverflow.com/questions/6988849/how-to-reset-jenkins-security-settings-from-the-command-line>
>>>>>>  *
>>>>>>
>>>>>>
>>>>>> *On Thu, Sep 6, 2018 at 1:04 PM Steve Burrus >>>>> > wrote:*
>>>>>>
>>>>>>> *I keep on disinstalling/reinstaling Jenkins because of my
>>>>>>> forgetting wh at my login information is. I have read  that my password 
>>>>>>> is
>>>>>>> stored in a "secrets" file but I haven't been able to access it yet. Can
>>>>>>> someone hel

Re: Need Login Help

[Mark Waite]

The file jenkins.exe.config controls the way Windows executes the program
"jenkins.exe".  It does not store the global Jenkins configuration.

The global Jenkins configuration (including the  setting) is
stored in a file named "config.xml".  The file that needs to be modified is
not named "jenkins.exe.config", it is named "config.xml".

If you search your file system (Windows search, or with a find command) for
a file which contains the text "true" and is
named "config.xml", that is the file.  A file of any other name won't do.
Adding the text to any other file won't do.

All the best!
Mark Waite


On Thu, Sep 6, 2018 at 7:59 PM Steve Burrus  wrote:

> Mark here is what I have in my "C:\MyJenkins\jenkins.exe.config" file.Here
> is what I have inside the file :
> 
>   
> 
>   
>   
> 
> 
>   
> 
> Now should I put that  line in THIS file, and
> if so where?
>
>
> On Thu, Sep 6, 2018 at 8:09 PM Mark Waite 
> wrote:
>
>> It depends on how you are running Jenkins.
>>
>> If you are running Jenkins from a command line using the war file, like:
>>
>> C:\Users\Mark\my-jenkins> java -jar jenkins.war
>>
>> then the Jenkins HOME directory is placed in the ".jenkins" subdirectory
>> of your home directory.  In my case, that means I have:
>>
>> C:\Users\Mark\.jenkins\config.xml
>>
>> that contains the line 'true'
>>
>> If you are running Jenkins as configured with the MSI installer, then the
>> file is:
>>
>> C:\Program Files (x86)\Jenkins\config.xml
>>
>> If you've modified your installation by setting a value for JENKINS_HOME
>> before starting Jenkins, then that is where it was placed.
>>
>> If none of those match your installation, please describe in more detail
>> how you have installed Jenkins on your Windows 10 machine.
>>
>> Mark Waite
>>
>> On Thu, Sep 6, 2018 at 5:03 PM Steve Burrus  wrote:
>>
>>> *I'm sorry but I can't find that config.xml file in my Windows 10
>>> enterprise system. How exactly can I get to it?  I have ON the setting
>>> "Show Hidden Files and Folders".  *
>>>
>>>
>>>
>>> *On Thu, Sep 6, 2018 at 4:55 PM Mark Waite >> > wrote:*
>>>
>>>>
>>>> *https://stackoverflow.com/questions/6988849/how-to-reset-jenkins-security-settings-from-the-command-line
>>>> <https://stackoverflow.com/questions/6988849/how-to-reset-jenkins-security-settings-from-the-command-line>
>>>>  *
>>>>
>>>>
>>>> *On Thu, Sep 6, 2018 at 1:04 PM Steve Burrus >>> > wrote:*
>>>>
>>>>> *I keep on disinstalling/reinstaling Jenkins because of my forgetting
>>>>> wh at my login information is. I have read  that my password is stored in 
>>>>> a
>>>>> "secrets" file but I haven't been able to access it yet. Can someone help
>>>>> me with this?*
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> * -- 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/CABinwmWNORhXwDUEg1oE87-Bog4ZA6aCzfG3uzj3QjMJZKmSdw%40mail.gmail.com
>>>>> <https://groups.google.com/d/msgid/jenkinsci-users/CABinwmWNORhXwDUEg1oE87-Bog4ZA6aCzfG3uzj3QjMJZKmSdw%40mail.gmail.com?utm_medium=email_source=footer>.
>>>>> For more options, visit https://groups.google.com/d/optout
>>>>> <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/CAO49JtE6a0dVkMFMXWKM4O3i_snowSzcT%3D79SnDJ4CxLdVN3ow%40mail.gmail.com
>>>> <

Re: What is the System requirement for installing jenkins in linux prod Environemnt

[Mark Waite]

https://jenkins.io/doc/book/installing/ describes some general guidelines
for a Linux based installation of Jenkins.

Mark Waite

On Wed, Sep 5, 2018 at 5:29 AM Vowner  wrote:

> Hello Experts,
>
> Please help me with the Jenkins system requirement to setup in linux
> production environment.
>
>
> --
> 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/1e71bccd-3ed8-43e5-9f2f-44a71f3821f5%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/1e71bccd-3ed8-43e5-9f2f-44a71f3821f5%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFW5x8Jho3ncXDcH-oo-qZLwRwXj9qwoz2xoM9q_iu44A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Need Login Help

[Mark Waite]

It depends on how you are running Jenkins.

If you are running Jenkins from a command line using the war file, like:

C:\Users\Mark\my-jenkins> java -jar jenkins.war

then the Jenkins HOME directory is placed in the ".jenkins" subdirectory of
your home directory.  In my case, that means I have:

C:\Users\Mark\.jenkins\config.xml

that contains the line 'true'

If you are running Jenkins as configured with the MSI installer, then the
file is:

C:\Program Files (x86)\Jenkins\config.xml

If you've modified your installation by setting a value for JENKINS_HOME
before starting Jenkins, then that is where it was placed.

If none of those match your installation, please describe in more detail
how you have installed Jenkins on your Windows 10 machine.

Mark Waite

On Thu, Sep 6, 2018 at 5:03 PM Steve Burrus  wrote:

> *I'm sorry but I can't find that config.xml file in my Windows 10
> enterprise system. How exactly can I get to it?  I have ON the setting
> "Show Hidden Files and Folders".  *
>
>
>
> *On Thu, Sep 6, 2018 at 4:55 PM Mark Waite  > wrote:*
>
>>
>> *https://stackoverflow.com/questions/6988849/how-to-reset-jenkins-security-settings-from-the-command-line
>> <https://stackoverflow.com/questions/6988849/how-to-reset-jenkins-security-settings-from-the-command-line>
>>  *
>>
>>
>> *On Thu, Sep 6, 2018 at 1:04 PM Steve Burrus > > wrote:*
>>
>>> *I keep on disinstalling/reinstaling Jenkins because of my forgetting wh
>>> at my login information is. I have read  that my password is stored in a
>>> "secrets" file but I haven't been able to access it yet. Can someone help
>>> me with this?*
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> * -- 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/CABinwmWNORhXwDUEg1oE87-Bog4ZA6aCzfG3uzj3QjMJZKmSdw%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/CABinwmWNORhXwDUEg1oE87-Bog4ZA6aCzfG3uzj3QjMJZKmSdw%40mail.gmail.com?utm_medium=email_source=footer>.
>>> For more options, visit https://groups.google.com/d/optout
>>> <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/CAO49JtE6a0dVkMFMXWKM4O3i_snowSzcT%3D79SnDJ4CxLdVN3ow%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtE6a0dVkMFMXWKM4O3i_snowSzcT%3D79SnDJ4CxLdVN3ow%40mail.gmail.com?utm_medium=email_source=footer>.*
>
>
>> * For more options, visit https://groups.google.com/d/optout
>> <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/CABinwmU6LigSKmYkjCZKVmT%3Dsh0idB4iweVapX8i53Hk11Q9nw%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CABinwmU6LigSKmYkjCZKVmT%3Dsh0idB4iweVapX8i53Hk11Q9nw%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFS6tZBqAdUvekjs75%3DEsWbPKgCWZPAP8a92iJ6pNLPmA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Need Login Help

[Mark Waite]

https://stackoverflow.com/questions/6988849/how-to-reset-jenkins-security-settings-from-the-command-line


On Thu, Sep 6, 2018 at 1:04 PM Steve Burrus  wrote:

> *I keep on disinstalling/reinstaling Jenkins because of my forgetting wh
> at my login information is. I have read  that my password is stored in a
> "secrets" file but I haven't been able to access it yet. Can someone help
> me with this?*
>
>
>
>
>
> --
> 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/CABinwmWNORhXwDUEg1oE87-Bog4ZA6aCzfG3uzj3QjMJZKmSdw%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/CAO49JtE6a0dVkMFMXWKM4O3i_snowSzcT%3D79SnDJ4CxLdVN3ow%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Running Jenkins in Docker on Windows 7 - missing info on Getting started with the Guided Tour page

[Mark Waite]

Docker on Windows requires Windows 10.  Running Docker on Windows 7
requires a workaround.  The tutorial is stating correct information.

It is also correct to perform the steps as described in the tutorial.  The
tutorial says:

Download and run Jenkins
<https://jenkins.io/doc/pipeline/tour/getting-started/#download-and-run-jenkins>

   1.

   Download Jenkins
   <http://mirrors.jenkins.io/war-stable/latest/jenkins.war>.
   2.

   Open up a terminal in the download directory.
   3.

   Run java -jar jenkins.war --httpPort=8080.
   4.

   Browse to http://localhost:8080.
   5.

   Follow the instructions to complete the installation.


The Jenkins executable file (jenkins.war) is downloaded (by the browser of
your choice or wget or curl or another program).  Open a Windows command
prompt window (terminal) in the download directory.  Assure that Java 8 is
the Java version you're running (`java -version`).  Run java -jar
jenkins.war

Once that is running, open a web browser to http://localhost:8080/

None of those steps have involved Docker in any way.  The requirement for
Docker comes later in the tutorial.  The tutorial is trying to state all
the requirements in advance.  Those first 5 steps don't use Docker.

Thanks!
Mark Waite

On Sat, Sep 1, 2018 at 6:34 AM Tony C  wrote:

> That tutorial states that Docker requires Windows 10, and that installing
> the Docker Toolbox on Windows 7 and other platforms, is a *required*.
> workaround.
>
>
> On Thursday, August 30, 2018 at 9:21:42 PM UTC-7, Mark Waite wrote:
>
>> The example intentionally has you run Jenkins without using Docker.  The
>> requirement for Docker comes in later steps of that tutorial.
>>
>> On Thu, Aug 30, 2018 at 5:53 PM Tony C  wrote:
>>
>
>>> Under Prerequisites,
>>>
>>> I've just installed the Docker toolbox on Windows 7 as directed by this
>>> page:
>>>
>>> https://jenkins.io/doc/pipeline/tour/getting-started/
>>>
>>> Under Download and run Jenkins
>>> downloading jenkins.war is *outside *of Docker.
>>>
>>> How do you download & run jenkins.war INSIDE of the Docker image?
>>>
>>> I think there is a huge disconnect on this page.- >
>>> https://jenkins.io/doc/pipeline/tour/getting-started/
>>>
>>> --
>>> 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/89d2025f-efe6-48e9-ad36-be4a547efc3b%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/89d2025f-efe6-48e9-ad36-be4a547efc3b%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/26394537-d7a4-4448-9c97-f9467424d7e7%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/26394537-d7a4-4448-9c97-f9467424d7e7%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEbH0jfgwQuZSaNBw_VyUwprCMm0R5kCYTBmWJ5GUSHFg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Howto change the output/workspace of a git clone job?

[Mark Waite]

Jenkins generally prefers that workspaces are not hard-coded locations on
specific machines.  Setting a workspace as a hard-coded location causes
problems like:

   - Only one build can run at a time (throughput limit)
   - Only one machine can run the build (performance limit)
   - Source repository is copied into the workspace (undesirable for
   websites since it risks making your site history available through your web
   server accidentally)
   - Accidental tool and file system dependencies are not detected because
   the same machine and dir is used for every build

Rather than using /srv/www/htdocs as a Jenkins workspace, you should create
a "deploy step" in your build process that copies from a working directory
(assigned by Jenkins automatically) to /srv/www/htdocs after all the build
and verification steps are complete.

Mark Waite

On Thu, Aug 30, 2018 at 9:43 AM Gorgonz ola  wrote:

> env: opensuse leap 15
>
> well, I'm completely new in using jenkins. In fact I just did my first
> project, that only clones a specific git branch and thats it.
>
> This works fine and the files are copied to /var/lib/jenkins/workspace.
>
> But it is a website project, where I prefer /srv/www/htdocs/.
>
> Where do I have to set this alternative workspace?
>
> Any suggestions?
>
> --
> 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/57e3040e-0c93-48df-b87b-cfcf8b5f6db6%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/57e3040e-0c93-48df-b87b-cfcf8b5f6db6%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFpzZBwvUh394U%2B6Q4eG2he_h6AjF2r863Tf6aEYucsDA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: JNLP java.nio.channels.ClosedChannelException with kubernetes-plugin

[Mark Waite]

Does the pod template meet the Kubernetes plugin constraints
 mentioned in
readme? Specifically, is ttyEnabled and is there a long-running process
that will allow the pod to continue running until the job completes?

On Sat, Aug 25, 2018 at 4:58 PM  wrote:

> I'm using Kubernetes plugin 1.12.3
>
> The plugin works well, but whenever the agent does streams the log to the
> master, it causes a connection exception as follows.
> To reproduce, simply create a free style job, restrict to run on the
> kubernetes pod, and add a step to sleep for 300 seconds.
>
>
> FATAL: command execution failed
> java.nio.channels.ClosedChannelException
>   at 
> org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
>   at 
> org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:142)
>   at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795)
>   at 
> jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
>   at 
> jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at java.lang.Thread.run(Thread.java:748)
> Caused: java.io.IOException: Backing channel 'JNLP4-connect connection from 
> ip-192-168-247-3.us-west-2.compute.internal/192.168.247.3:23684' is 
> disconnected.
>   at 
> hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:214)
>   at 
> hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283)
>   at com.sun.proxy.$Proxy110.isAlive(Unknown Source)
>   at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1137)
>   at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1129)
>   at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:155)
>   at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:109)
>   at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
>   at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
>   at hudson.model.Build$BuildExecution.build(Build.java:206)
>   at hudson.model.Build$BuildExecution.doRun(Build.java:163)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
>   at hudson.model.Run.execute(Run.java:1798)
>   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
>   at hudson.model.ResourceController.execute(ResourceController.java:97)
>   at hudson.model.Executor.run(Executor.java:429)
> FATAL: Unable to delete script file /tmp/jenkins5788393309854271460.sh
> java.nio.channels.ClosedChannelException
>   at 
> org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
>   at 
> org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:142)
>   at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795)
>   at 
> jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
>   at 
> jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at java.lang.Thread.run(Thread.java:748)
> Caused: hudson.remoting.ChannelClosedException: Channel "unknown": Remote 
> call on JNLP4-connect connection from 
> ip-192-168-247-3.us-west-2.compute.internal/192.168.247.3:23684 failed. The 
> channel is closing down or has closed down
>   at hudson.remoting.Channel.call(Channel.java:948)
>   at hudson.FilePath.act(FilePath.java:1036)
>   at hudson.FilePath.act(FilePath.java:1025)
>   at hudson.FilePath.delete(FilePath.java:1511)
>   at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:123)
>   at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
>   at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
>   at hudson.model.Build$BuildExecution.build(Build.java:206)
>   at hudson.model.Build$BuildExecution.doRun(Build.java:163)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
>   at hudson.model.Run.execute(Run.java:1798)
>   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
>   at hudson.model.ResourceController.execute(ResourceController.java:97)
>   at hudson.model.Executor.run(Executor.java:429)
> Build step 

Re: Help staff the Contributors Corner at DevOps World | Jenkins World 2018

[Mark Waite]

Thanks Slide!

I'll include you on those topics.  I assume San Francisco only unless you
tell me that you'll also be in Nice.

Mark Waite

On Mon, Aug 20, 2018 at 8:38 PM Slide  wrote:

> See response inline below. Thanks for leading this effort!
>
> On Mon, Aug 20, 2018, 17:56 Mark Waite  wrote:
>
>> We want more people to help the Jenkins project in many different ways.
>> The Contributors Corner at DevOps World | Jenkins World 2018 is your chance
>> to help others as they learn how to help the Jenkins project.
>>
>> If you're attending DevOps World | Jenkins World 2018 in either San
>> Francisco or Nice, and would be willing to give 30 minutes or an hour to
>> assist at the Contributor's Corner table, we'd love to have your help.
>>
>> We've assigned themes to different time slots during the conference.
>> We'll staff the table with people experienced in that theme.  The
>> experienced people will help others contribute and become more experienced
>> in that specific area.  You can help new contributors as they learn how to
>> help the Jenkins project.
>>
>> Themes we've chosen:
>>
>>- Answer Jenkins Questions
>>
>> I can help with this one
>
>>
>>- Promoting Jenkins in Your Company
>>- Documenting Jenkins
>>- Localizing Jenkins
>>- Testing Jenkins Plugins (PRs and more)
>>
>> I can help with this one
>
>>
>>- Reviewing Jenkins Bugs
>>
>> I can help with this onr
>
>>
>>- Testing Jenkins
>>- Supporting Jenkins Platforms
>>- Organizing a Jenkins Area Meetup
>>- Helping Jenkins Infrastructure
>>
>> I can help with this one
>
>>
>>- Adopt a Jenkins Plugin
>>
>> I can help with this one
>
> If you're willing to assist new contributors as they learn how to help
>> within one or more of those themes during the conference, reply to this
>> message and I'll include you in the list.
>>
>> If you have suggestions for additional themes, send them to me.
>>
>> Thanks,
>> Mark Waite
>>
>> --
>>
> 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/CAO49JtGZMu-gZknUqGNKxbb94FOJS1Uu%3DO7h8CmM0P3iWECdWg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGZMu-gZknUqGNKxbb94FOJS1Uu%3DO7h8CmM0P3iWECdWg%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVd1g%2B-ghjMBS8hqXTn%3D%2BCdEEQo6xzHAB3nMNtzmZFNYFw%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVd1g%2B-ghjMBS8hqXTn%3D%2BCdEEQo6xzHAB3nMNtzmZFNYFw%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFedi-bOxPbw1XxqKz1JLGpPPwXUTgoavT-Quk%3D_u_QyQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help staff the Contributors Corner at DevOps World | Jenkins World 2018

[Mark Waite]

Thanks Ulli!  Will you be attending in San Francisco, or Nice, or both?

On Thu, Aug 23, 2018 at 4:41 PM Ullrich Hafner 
wrote:

> Am 21.08.2018 um 02:56 schrieb Mark Waite :
>
> We want more people to help the Jenkins project in many different ways.
> The Contributors Corner at DevOps World | Jenkins World 2018 is your chance
> to help others as they learn how to help the Jenkins project.
>
> If you're attending DevOps World | Jenkins World 2018 in either San
> Francisco or Nice, and would be willing to give 30 minutes or an hour to
> assist at the Contributor's Corner table, we'd love to have your help.
>
> We've assigned themes to different time slots during the conference.
> We'll staff the table with people experienced in that theme.  The
> experienced people will help others contribute and become more experienced
> in that specific area.  You can help new contributors as they learn how to
> help the Jenkins project.
>
> Themes we've chosen:
>
>- Answer Jenkins Questions
>- Promoting Jenkins in Your Company
>- Documenting Jenkins
>- Localizing Jenkins
>- Testing Jenkins Plugins (PRs and more)
>- Reviewing Jenkins Bugs
>- Testing Jenkins
>- Supporting Jenkins Platforms
>- Organizing a Jenkins Area Meetup
>- Helping Jenkins Infrastructure
>- Adopt a Jenkins Plugin
>
> If you're willing to assist new contributors as they learn how to help
> within one or more of those themes during the conference, reply to this
> message and I'll include you in the list.
>
>
> I can help with these themes:
> • Testing Jenkins Plugins (PRs and more)
> • Reviewing Jenkins Bugs
> • Testing Jenkins
> • Adopt a Jenkins Plugin
>
> Ulli
>
>
> If you have suggestions for additional themes, send them to me.
>
> Thanks,
> Mark Waite
>
> --
> 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/CAO49JtGZMu-gZknUqGNKxbb94FOJS1Uu%3DO7h8CmM0P3iWECdWg%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGZMu-gZknUqGNKxbb94FOJS1Uu%3DO7h8CmM0P3iWECdWg%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/81D378D8-D5E3-4BFE-8678-9D93473A328B%40gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/81D378D8-D5E3-4BFE-8678-9D93473A328B%40gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEtEFSsS6KsSdBi3pFDH_Q1OTx5ZX0fDMcG9N_TZZCFYQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: java.lang.NoSuchMethodError: No such DSL method 'pipeline' found among steps

[Mark Waite]

Can you explain further what you mean when you say that the file was
formatted with UTF-8?

As an example, I have a scripted Pipeline Jenkinsfile
<https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-6203/Jenkinsfile>
which
includes Japanese characters and is well-behaved.  I am reasonably certain
that it is UTF-8.  I have a declarative Jenkinsfile
<https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-52844/Jenkinsfile>
which also includes Japanese characters and is well-behaved.

Does the file you are editing use a byte-order mark to indicate that it is
UTF-8?

Is there some other technique that indicates it is a UTF-8 file?

If you can provide steps to duplicate the problem, feel free to upload
those steps to JENKINS-52844, or to create a new bug report if you believe
that the bug you're seeing does not match JENKINS-52844.

Mark Waite

On Tue, Aug 21, 2018 at 2:33 PM Pablo Gandulfo 
wrote:

> I got this error and invested a considerable amount of time to solve it,
> searching on internet and trying different approaches, all of them with no
> success. Finally, I found the cause and solve it. So, I would like to share
> this knowledge and I hope that someone at Jenkins Developer Team document
> this to avoid others facing the same problem.
>
> The cause was that the Jenkinsfile was formatted with UTF-8. That's it!
> Firstly I was using it in ANSI, but some latin characters were appearing
> wrongly in the log. So I changed to UTF-8 and, suddenly, every first work I
> used in the script file (pipeline, node, def, etc.) didn't work anymore,
> throwing the same error: "java.lang.NoSuchMethodError: No such DSL method
> 'X' found among steps".
>
> I imagine that this may be the cause of JENKINS-52844 , which was opened
> recently. So, Andrew Bayer (@abayer), I hope you see this message too.
>
> Regards,
> Pablo.
>
> --
> 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/0d435cdd-0669-4ed5-9142-bb58730bece6%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/0d435cdd-0669-4ed5-9142-bb58730bece6%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtENsx1iQLJ7kT01SAr-XQO9S7nkMd-Y7u0OirdqUtOXUw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help staff the Contributors Corner at DevOps World | Jenkins World 2018

[Mark Waite]

Yes, this does not replace a ticket to Jenkins World, nor does it cover any
other costs.

Mark Waite

On Mon, Aug 20, 2018 at 7:16 PM su suren  wrote:

> I love to this. But I still have to buy a ticket. Yea?
>
> su suren
> 邮箱：linuxsu...@gmail.com
>
> <https://maas.mail.163.com/dashi-web-extend/html/proSignature.html?iconUrl=http%3A%2F%2Fmail-online.nosdn.127.net%2Faded916316efb8d67fc36054c88f2d09.jpg=su+suren=linuxsuren%40gmail.com=1=%5B%22%E9%82%AE%E7%AE%B1%EF%BC%9Alinuxsuren%40gmail.com%22%5D>
>
> 签名由 网易邮箱大师 <https://mail.163.com/dashi/dlpro.html?from=mail88> 定制
>
> On 08/21/2018 08:56, Mark Waite  wrote:
> We want more people to help the Jenkins project in many different ways.
> The Contributors Corner at DevOps World | Jenkins World 2018 is your chance
> to help others as they learn how to help the Jenkins project.
>
> If you're attending DevOps World | Jenkins World 2018 in either San
> Francisco or Nice, and would be willing to give 30 minutes or an hour to
> assist at the Contributor's Corner table, we'd love to have your help.
>
> We've assigned themes to different time slots during the conference.
> We'll staff the table with people experienced in that theme.  The
> experienced people will help others contribute and become more experienced
> in that specific area.  You can help new contributors as they learn how to
> help the Jenkins project.
>
> Themes we've chosen:
>
>- Answer Jenkins Questions
>- Promoting Jenkins in Your Company
>- Documenting Jenkins
>- Localizing Jenkins
>- Testing Jenkins Plugins (PRs and more)
>- Reviewing Jenkins Bugs
>- Testing Jenkins
>- Supporting Jenkins Platforms
>- Organizing a Jenkins Area Meetup
>- Helping Jenkins Infrastructure
>- Adopt a Jenkins Plugin
>
> If you're willing to assist new contributors as they learn how to help
> within one or more of those themes during the conference, reply to this
> message and I'll include you in the list.
>
> If you have suggestions for additional themes, send them to me.
>
> Thanks,
> Mark Waite
>
> --
> 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/CAO49JtGZMu-gZknUqGNKxbb94FOJS1Uu%3DO7h8CmM0P3iWECdWg%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGZMu-gZknUqGNKxbb94FOJS1Uu%3DO7h8CmM0P3iWECdWg%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/1534814153325.y5g40wt2y3tisoltu5voxxc2%40android.mail.163.com
> <https://groups.google.com/d/msgid/jenkinsci-users/1534814153325.y5g40wt2y3tisoltu5voxxc2%40android.mail.163.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFS6JzDYEmWLUCKKmYsoaiT0wo5aC5YQ71y%3DEPeVEQZ_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Help staff the Contributors Corner at DevOps World | Jenkins World 2018

[Mark Waite]

We want more people to help the Jenkins project in many different ways.
The Contributors Corner at DevOps World | Jenkins World 2018 is your chance
to help others as they learn how to help the Jenkins project.

If you're attending DevOps World | Jenkins World 2018 in either San
Francisco or Nice, and would be willing to give 30 minutes or an hour to
assist at the Contributor's Corner table, we'd love to have your help.

We've assigned themes to different time slots during the conference.  We'll
staff the table with people experienced in that theme.  The experienced
people will help others contribute and become more experienced in that
specific area.  You can help new contributors as they learn how to help the
Jenkins project.

Themes we've chosen:

   - Answer Jenkins Questions
   - Promoting Jenkins in Your Company
   - Documenting Jenkins
   - Localizing Jenkins
   - Testing Jenkins Plugins (PRs and more)
   - Reviewing Jenkins Bugs
   - Testing Jenkins
   - Supporting Jenkins Platforms
   - Organizing a Jenkins Area Meetup
   - Helping Jenkins Infrastructure
   - Adopt a Jenkins Plugin

If you're willing to assist new contributors as they learn how to help
within one or more of those themes during the conference, reply to this
message and I'll include you in the list.

If you have suggestions for additional themes, send them to me.

Thanks,
Mark Waite

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

Re: Is Jenkins right for me (orchestration of unix command line, akin to cron)?

[Mark Waite]

Jenkins can orchestrate tasks that are not related to continuous
integration.

I've used it as a web interface to regularly scheduled jobs like cron.
However, if that is its only use, then I think that is more software than
you need.

If you need to present graphs, charts and tables from one run to the next
and if those graphs, charts and tables can be represented in Jenkins, then
it makes sense (to me) to also use it to orchestrate your scheduled tasks.

If you need to refer to the history of task execution from a web interface,
then Jenkins is well-suited.  Then it makes sense (to me) to also use it to
orchestrate your scheduled tasks.

I often refer to the execution history of specific jobs to identify why
they failed and how to improve them.  The web interface makes that easier
for me than filtering through my e-mail box for the output from cron jobs.

Mark Waite

On Mon, Aug 20, 2018 at 3:34 AM ChrizK  wrote:

> Hi Mark
>
> Thanks for taking the time to reply, it is appreciated.
>
> Reading the BlazeMeter blog has prompted me to add one (perhaps important)
> comment ...
> My use has absolutely nothing to do with Software Development/CI.
> The load test is related to a telecoms environment, producing traffic
> emulating calls (RADIUS, DIAMETER/Gx/Gy, User Plane/Internet etc).
>
> Given this additional information, would Jenkins still be considered a
> good option?
>
> Regards
>
>
> On Friday, 17 August 2018 18:34:01 UTC+1, Mark Waite wrote:
>
>> Jenkins can orchestrate tasks, including build, test, and deploy.  The
>> folks at BlazeMeter have a great blog post
>> <https://www.blazemeter.com/blog/continuous-integration-101-how-run-jmeter-jenkins>
>> that highlights ways to run Apache JMeter with Jenkins.  There is also a 2015
>> research paper
>> <https://www.researchgate.net/publication/274738961/download> on
>> integrating performance testing into Jenkins builds.
>>
>> The "how" question depends very much on the specifics of your load
>> testing tool, how you would like to present the results, and how much
>> effort you want to spend to do it.
>>
>> Mark Waite
>>
>> On Fri, Aug 17, 2018 at 10:10 AM ChrizK  wrote:
>>
> As an initial warning, I am COMPLETELY new to Jenkins.
>>> I have never installed it, or seen it running.
>>> My manager gave me a task, saying that a team member had suggested
>>> Jenkins.
>>>
>>> We have an in-house load test tool, which runs on multiple nodes,
>>> resulting in significant load (millions of connections).
>>> We need to orchestrate the initialisation of each node, and I perceive
>>> the need to monitor the execution, restart on failure, and terminate at a
>>> given point (assumed to be time).
>>>
>>> Actually, I haven't even seen the load test tool yet, as I have only
>>> just (re)joined the team after several years.
>>> I am assuming it is a unix/linux command line executable with
>>> parameters, or perhaps a config script which may need adapting for each run.
>>>
>>> Hopefully that is enough information to get started.
>>>
>>> So, my initial questoin is, does Jenkins suit the purpose?
>>> ...and my follow on questoin(s) will be, how!
>>>
>>> (I have been viewing youtube/googling all day.  All I have found that
>>> appears to be relevant, are references to Execute Shell, and some 'pro'
>>> Jenkins blogs on switching from CRON. One blog indicates that Jenkins would
>>> be installed on each machine, but my perception is a single, stand alone,
>>> server, which orchestrates multiple nodes, by SSH login, command execution
>>> and monitoring ...but perhaps, I am way off)
>>>
>>> Thank you in advance for any help.
>>>
>>> Also, is this the main forum for Jenkins?  I was surprised there wasn't
>>> one on their site,which appears to favour a chat facility (which doesn't
>>> seem very practical when looking for advice around the globe).
>>>
>>> Kind Regards
>>>
>>> --
>>> 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/6429acff-f41a-4f3d-928c-949eec643578%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/6429acff-f41a-4f3d-928c-949eec643578%40googlegroups.com?utm_medium=email_source

Re: Is Jenkins right for me (orchestration of unix command line, akin to cron)?

[Mark Waite]

Jenkins can orchestrate tasks, including build, test, and deploy.  The
folks at BlazeMeter have a great blog post
<https://www.blazemeter.com/blog/continuous-integration-101-how-run-jmeter-jenkins>
that highlights ways to run Apache JMeter with Jenkins.  There is also a 2015
research paper <https://www.researchgate.net/publication/274738961/download>
on integrating performance testing into Jenkins builds.

The "how" question depends very much on the specifics of your load testing
tool, how you would like to present the results, and how much effort you
want to spend to do it.

Mark Waite

On Fri, Aug 17, 2018 at 10:10 AM ChrizK  wrote:

> As an initial warning, I am COMPLETELY new to Jenkins.
> I have never installed it, or seen it running.
> My manager gave me a task, saying that a team member had suggested Jenkins.
>
> We have an in-house load test tool, which runs on multiple nodes,
> resulting in significant load (millions of connections).
> We need to orchestrate the initialisation of each node, and I perceive the
> need to monitor the execution, restart on failure, and terminate at a given
> point (assumed to be time).
>
> Actually, I haven't even seen the load test tool yet, as I have only just
> (re)joined the team after several years.
> I am assuming it is a unix/linux command line executable with parameters,
> or perhaps a config script which may need adapting for each run.
>
> Hopefully that is enough information to get started.
>
> So, my initial questoin is, does Jenkins suit the purpose?
> ...and my follow on questoin(s) will be, how!
>
> (I have been viewing youtube/googling all day.  All I have found that
> appears to be relevant, are references to Execute Shell, and some 'pro'
> Jenkins blogs on switching from CRON. One blog indicates that Jenkins would
> be installed on each machine, but my perception is a single, stand alone,
> server, which orchestrates multiple nodes, by SSH login, command execution
> and monitoring ...but perhaps, I am way off)
>
> Thank you in advance for any help.
>
> Also, is this the main forum for Jenkins?  I was surprised there wasn't
> one on their site,which appears to favour a chat facility (which doesn't
> seem very practical when looking for advice around the globe).
>
> Kind Regards
>
> --
> 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/6429acff-f41a-4f3d-928c-949eec643578%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/6429acff-f41a-4f3d-928c-949eec643578%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtH74Ki2AAeZacTr4%3Dczo_3kbM2BJggG6jiUzCkTxNJ64A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline git an LFS project

[Mark Waite]

https://jenkins.io/blog/2017/10/02/pipeline-templates-with-shared-libraries/
describes
how a Pipeline shared library can extract common statements from a
declarative Pipeline to simplify the declarative Pipeline.

There isn't a way to perform a git LFS fetch or checkout with the "git"
step.  The "git" step is a simplified form of the "checkout" step.  It
intentionally does not include all the options and capabilities of the
"checkout" step.

Mark Waite

On Fri, Aug 17, 2018 at 7:42 AM Leandro Cofre  wrote:

> Hi,
>
> I have a pipeline where I checkout two repositories, one with source code
> and the other with binaries that are part of the release. The latter uses
> the LFS git plugin.
>
> My question is if there's a simpler way to declare I want to clone a git
> LFS repo other than the one I write below. The other repo description looks
> much simpler.
>
> I also noticed the configuration for the LFS repo left the HEAD detached.
>
> Thanks very much for your help.
>
>
> pipeline {
> agent any
>
> stages {
> stage('Checkout') {
> steps {
> dir('content') {
> checkout scm: [
> $class: 'GitSCM',
> branches: [[name: 'refs/heads/master']],
> extensions: [[$class: 'GitLFSPull']],
> userRemoteConfigs: [[
> credentialsId: 'TheID',
> url: '
> https://bitbucket.org/COMPANY/content.git'
> ]]
> ]
> }
>
>
> dir('source') {
> git branch: 'master',
> url: 'https://bitbucket.org/COMPANY/source.git',
> credentialsId: 'TheID'
> }
> }
> }
> stage('Build') {
> steps {
> echo 'Building'
> }
> }
> stage('Deploy') {
> steps {
> echo 'Deploying'
> }
> }
> }
> }
>
> --
> 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/ec91fa16-de19-4b1b-aa11-0b3559418afb%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/ec91fa16-de19-4b1b-aa11-0b3559418afb%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFz0wZN4tjSfcBPRJoxTRa-AwCGeTnzNM2AaLTQWi723Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Specifing git branch via a parameter

[Mark Waite]

On Thursday, August 9, 2018 at 4:45:07 PM UTC-6, MDKF wrote:
>
> Hi All,
>  I have a pipeline that starts out like this:
>
> pipeline {
>>
>>  agent any
>>
>>  parameters {
>>
>> string(defaultValue: 'develop', description: 'branch', name: 
>>> 'Branch')
>>
>> }
>>
>>  stages {
>>
>>   stage('Checkout') {
>>
>>steps {
>>
>> checkout([$class: 'GitSCM', branches: [
>>
>>  [name: 'refs/remotes/origin/${params.Branch}']
>>
>>
String expansion in groovy happens inside a double-quoted string and does 
not happen inside a single-quoted string.  Change to a 
double-quoted string.  You may also prefer the simpler form of: 

[name: params.Branch]

Mark Waite

When the project it runs because the parameter isn't being inserted.:
>
>> > C:\Program Files (x86)\Git\cmd\git.exe rev-parse 
>> "refs/remotes/origin/${params.Branch}^{commit}" # timeout=10
>> > C:\Program Files (x86)\Git\cmd\git.exe rev-parse 
>> "refs/remotes/origin/refs/remotes/origin/${params.Branch}^{commit}" # 
>> timeout=10 
>
> > C:\Program Files (x86)\Git\cmd\git.exe rev-parse 
>> "refs/remotes/origin/${params.Branch}^{commit}" # timeout=10 
>
>
> What am I doing wrong? Thanks,
> -Michael
>

-- 
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/21abbc0e-dfe8-47e0-9fa5-05fab1d8f0fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: pipeline script and git parameter plugin

[Mark Waite]

On Thursday, August 9, 2018 at 9:55:55 AM UTC-6, suoyua...@shopee.com wrote:
>
> Hi, I am running jenkins2 and pipeline for my job
>
> My pipeline definition is pipeline script(not pipeline script from SCM) 
> and I am using git as my scm system.
>
> I want to specify a git branch before a build starts. How can I do this?
>

If you know the list of branch names that you want to present in the list, 
you can use the Jenkins Minute 
video https://www.youtube.com/watch?v=5_tvlaIeQUQ as an example to 
parameterize the PIpeline job.

If you want the list of branches to be generated dynamically based on the 
contents of the repository, investigate the git parameter plugin 
at https://plugins.jenkins.io/git-parameter

Mark Waite

-- 
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/1b4ea70c-58e0-4364-807f-6a27fa1e2f73%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Create and push new git branch?

[Mark Waite]

The git plugin has no facility to support creating a branch or pushing a
branch from a Pipeline step.

However, Pipeline can do it with an "sh" or "bat" step (depending on your
platform).

If your repository URL is an ssh URL ( g...@example.com:dir/repo.git or ssh:
//g...@example.com/dir/repo.git ) then you would use place the sh or bat
step inside an ssh-agent block.  The ssh-agent block starts ssh-agent and
then command line git will use ssh-agent to authenticate.

If your repository is an http or https URL (
https://example.com/dir/repo.git ) then you would use place the sh or bat
step inside a withCredentials block.  The withCredentials block extracts
username and password from the Jenkins credentials and makes them available
as a variable.  Place that variable inside the git URL in the sh or bat
step as in "git push https://${USERNAME}:${PASSWORD}@example.com/dir/repo;.
There are examples of withCredentials on the jenkins.io site to give good
techniques.

Mark Waite

On Tue, Aug 7, 2018 at 6:24 PM  wrote:

> Hi folks,
>
> I've googled extensively, but I haven't seen any documentation or answers
> on how to create a new git branch in Pipeline. I must be missing something
> obvious, but the Git plugin page doesn't indicate anything other than
> checking out code with credentials. Has anyone here used Jenkins to create
> a branch and then push it to remote?
>
> Thanks!
> Jack
>
> --
> 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/22a42e16-f0df-4dad-9e1f-3996cae8d40a%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/22a42e16-f0df-4dad-9e1f-3996cae8d40a%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFn_4Zte%3DmQ_QLDB4JvGiVbt8GY3WbxaqB9hMTxqjM61g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Can i run master and slave on same machine

[Mark Waite]

Refer to
https://wiki.jenkins.io/display/JENKINS/Step+by+step+guide+to+set+up+master+and+slave+machines+on+Windows
 or https://stackoverflow.com/questions/24962504/adding-a-slave-to-jenkins
or
http://scmquest.com/jenkins-master-slave-setup-and-configuration-with-screenshots/
 or
http://scmquest.com/jenkins-windows-slave-configuration-with-screenshots/ .

If those don't solve the issue you're seeing, you'll need to provide more
details about the error "file available", including the steps you took with
precede that error and the alternatives you've tried to resolve the error.

Mark Waite

On Sun, Aug 5, 2018 at 10:42 PM Nehal Abdelhafez 
wrote:

>
> can you just tell me how i can run master and slave on the same machine i
> have install and run a master and i cant make the slave join it gives error
> "file avaliable " thanks in advance
>
> On Wednesday, June 27, 2012 at 4:26:03 PM UTC+2, Mark Waite wrote:
>>
>> The simplest answer to your "Can I run master and slave on the same
>> machine" is "Yes".  The challenging part of the question is "Why?"
>>
>> The subject line seems to hint that you are considering running a master
>> and a slave on the same machine.  It certainly can be done.  Whether it
>> should be done depends on your reason for wanting to use a slave.
>>
>> The Jenkins master can run multiple jobs in parallel so long as you allow
>> have enough executors defined on the master node to host your parallel
>> jobs.  If the master machine has enough compute power to perform all the
>> parallel jobs, then executing all the jobs on the master node is simpler
>> because it is easier to administer one machine (the master) than two
>> machines (the master and the slave).
>>
>> If the master machine does not have enough compute power to perform all
>> the parallel jobs, then additional computers can be added as slave nodes to
>> add compute power.
>>
>> Another use of master and slave is when different configurations are
>> needed.  For example, I have a master node that is 64 bit Linux and slave
>> nodes for 32 bit Linux, 32 bit Windows, and 64 bit Windows.  I couldn't run
>> that configuration without master and slave setups.
>>
>> I believe others have used a slave configuration to create a separate
>> configuration even on the same machine.  That is not a technique I've used,
>> but I've considered it, possibly using a slave running in a chroot
>> environment on a Linux machine to simulate a different configuration
>> without actually running on a different machine.
>>
>> It is also possible to run a master and a slave on the same machine
>> simply by configuring the slave node to use a different home directory than
>> the master node.  I'm not sure why you would do that, but it can be done.
>>
>> Mark Waite
>>
>>
>>
>> --
>> *From:* Varghese Renny 
>> *To:* jenkins...@googlegroups.com
>> *Sent:* Tuesday, June 26, 2012 8:53 PM
>> *Subject:* Can i run master and slave on same machine
>>
>>
>> I have a doubt regarding, if multipe jobs are there ,is it better to
>> distribute build on slave or
>> do it on master itself?
>> if i can do master and slave? how can i implement this?
>>
>>
>> --
> 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/0d3efd72-eed1-4a0f-8827-21b498374822%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/0d3efd72-eed1-4a0f-8827-21b498374822%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtESu5_rURAKYfKF8208WfcHpYnX-N15%2Bxjt7CD78-qc1Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is it possible to build and test 50 similarly named Github repos with a singe job?

[Mark Waite]

I think you're making your life more difficult than it needs to be.

The "GitHub Organization" plugin is no longer being developed because the
"GitHub Organization" project functionality has been included in other
plugins.  The "GitHub Organization" project type is alive and working very
well for many of us.  I suspect it is even the project type that is used on
ci.jenkins.io to automatically create a new folder of jobs each time a new
Jenkins plugin is added and each time a Jenkins plugin adds a Jenkinsfile.

Yes, you can probably find a way to use webhooks and triggers to
approximate some of the things that the GitHub Organization project does.
I don't think those webhooks and triggers will match what your students
will find as they become working programmers.  They will tend to see GitHub
Organization projects when they work at a company that uses GitHub.  They
will tend to see Bitbucket branch source projects when they work at a
company that uses Bitbucket.

You expressed concern that a student might change the contents of
the Jenkinsfile in their repository.  I think that is a good thing.  If
they decide that they want more tests or different tests or different types
of tests, they can add them.  If they decide that they want static analysis
with findbugs or spotbugs, they can extend the Jenkinsfile.  Since each
student has their own repository, I think you want the student to have the
autonomy to choose how their repository is built.

Mark Waite

On Fri, Jul 20, 2018 at 2:24 PM Mark  wrote:

> Multipipeline branch options the way to go here. But Buck the bugs answer
> a few down might help you create multiple stages from a flat file of your
> students names to help you create the branches.
>
>
> https://stackoverflow.com/questions/42837066/can-i-create-dynamically-stages-in-a-jenkins-pipeline
>
> On Fri, 20 Jul 2018, 13:27 Jan Monterrubio, 
> wrote:
>
>> This definitely sounds like what Mark suggested. If you set up the GitHub
>> service and webhook, Jenkins can build on every push to any branch in a
>> repository.
>>
>> You’ll need to make sure the repositories have a jenkinsfile:
>> https://jenkins.io/doc/book/pipeline/jenkinsfile/
>>
>> You’ll probably need some plugins like the GitHub branch source and maybe
>> GitHub organization.
>>
>> On Thu, Jul 19, 2018 at 22:43 Mark Waite 
>> wrote:
>>
>>> I think you want a "GitHub Organization" project.  It will scan an
>>> entire organization then create and destroy jobs based on the presence of a
>>> Jenkinsfile in the root directory of one or more branches in the
>>> repositories that it finds.
>>>
>>> Mark Waite.
>>>
>>> On Thu, Jul 19, 2018 at 9:26 PM Ted Cowan  wrote:
>>>
>>>> I am a college instructor that is automating the submission of
>>>> programming assignments using GitHub Classroom.  Typically we have 50
>>>> students, each submitting 9 assignments per semester.  All of the repos are
>>>> part of one organization, and I wish to trigger a build and test when each
>>>> student pushes to their private repo.
>>>>
>>>> Is this possible in Jenkins, and if so, how?  There are myriad examples
>>>> of how to trigger a build on a single repo, but I need to trigger the same
>>>> build when any of 50 repos are changed.  I hope this doesn't mean I have to
>>>> add the names of all 50 repos to each job, but that might be doable if I
>>>> edit the config.xml outside of Jenkins.
>>>>
>>>> ...ted
>>>>
>>>> --
>>>> 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/56757380-01d9-45ef-9123-b0b732ab819b%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-users/56757380-01d9-45ef-9123-b0b732ab819b%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/j

Re: Jenkins new git plugin which allows to ignore commits which are created by the automated Neustar commits.

[Mark Waite]

I'm not aware of a new git plugin. The existing git plugin allows freestyle
jobs to ignore commits based on author and based on content of the commit
message.  It does not allow multibranch pipeline jobs to ignore commits.

Mark Waite

On Fri, Aug 3, 2018, 5:39 AM  wrote:

> Hello,
>
> I need Jenkins new git plugin which allows to ignore commits, which are
> created by the automated Neustar commits..is their any new git plugin ??
>
>
> Thank you.
>
> *Regards*
> *Jai*
>
> --
> 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/727b8d64-7890-4620-86b1-dbd891897481%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/727b8d64-7890-4620-86b1-dbd891897481%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtE7Bw2y_-6Gb39vrx88CsE9rU26rVHvpQWd5zjUaENR8g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Global Git config update in Jenkins

[Mark Waite]

There isn't a way to configure those types of settings from the git plugin.

Can you explain why you want to set credential helper cache?

Mark Waite

On Wed, Aug 1, 2018 at 5:41 PM Nitish Goel  wrote:

> Hi ,
>
> I want to add few of git configuration as below in my jenkins so that this
> configuration is global to all git running jobs in any of the slave.
>
> git config lfs.activitytimeout 120
> git config lfs.transfer.maxretries 20
> git config –global credential.helper cache'
>
> Can you please let me know where I need to add these details? In my
> configuration, I do not see any configurations where I can provide these
> details.
>
> Git installations
> *Git*
>   Name
>   Path to Git executable [image: Help for feature: Path to Git executable]
> <https://bxb-nmtgci-01.cisco.com:9081/configure#>
> Install automatically
>
>
> Thanks,
> Nitish Goel
>
> --
> 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/f2e72213-6c6c-4c98-b3ec-c404d8722bf6%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/f2e72213-6c6c-4c98-b3ec-c404d8722bf6%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtE1_FEtaWOZRqp%2Bfjc7EV1Q5WGwnDyayy5V-X1kDYtZ8A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

[Mark Waite]

On Sun, May 20, 2018 at 6:52 PM Kernel Panic <netwarrior...@gmail.com>
wrote:

> Ok, I'll try to install a previous version manually , I have no option to
> Downgrade it from the UI, do you know which is the previous stable version
> to 3.9.0 ? or which one should I try with Jenkins 2.107.3 ?
>

Git plugin releases in the last 6 months: 3.9.0, 3.8.0, 3.7.0
Git client plugin releases in the last 6 months: 2.7.2, 2.7.1, 2.7.0

The message you're seeing is from the git client plugin, not the git
plugin.  Changing versions of the git plugin is unlikely to help.

All those versions are expected to work with Jenkins 2.107.3.  The plugin
pages (git <https://plugins.jenkins.io/git> and git client
<https://plugins.jenkins.io/git-client>)  include the changelogs for each
of those releases.


> Is there a way to run the plugin manually like "java something" to see if
> I can see any other error? I cannot find which is the dependency error or
> how to fix it, maybe a previous version works fine.
>

Sorry, but there isn't a command line way to simulate the problem you're
seeing.  I don't understand the problem you're seeing.

My personal hunch is that you may need to remove all cases where you have
both an hpi and a jpi file for the same plugin, remove the subdirectory of
the plugins directory for those cases (for example, if you have both a
git-client.jpi and a git-client.hpi, remove one of those two files and
remove "plugins/git-client" directory).

Mark Waite


> Thanks
> Regards
>
>
> El domingo, 20 de mayo de 2018, 21:45:25 (UTC-3), Mark Waite escribió:
>
>> Yes, it means that the git client plugin did not initialize correctly.
>> The git client plugin includes JGit.  That class (and the RemoteConfig
>> class) are classes from JGit which is included in the git client plugin.
>>
>> On Sun, May 20, 2018 at 6:24 PM Kernel Panic <netwar...@gmail.com> wrote:
>>
> Hi Mark
>>> Under Manage Old Data I found this, does it mean something to you?
>>>
>>> hudson.model.FreeStyleBuild project-name #82 NoClassDefFoundError:
>>> org/eclipse/jgit/lib/AnyObjectId
>>> El domingo, 20 de mayo de 2018, 20:36:48 (UTC-3), Mark Waite escribió:
>>>>
>>>>
>>>>
>>>> On Sun, May 20, 2018 at 5:32 PM Kernel Panic <netwar...@gmail.com>
>>>> wrote:
>>>>
>>>>> Ok, I'll play a bit with it, and what do you think about this error?
>>>>> does it mean anything? what happens if I remove or clean 
>>>>> /var/cache/jenkins
>>>>> directory? I can bet this is the root of cause, but no idea how to resolve
>>>>> that
>>>>> dependency error.
>>>>>
>>>>>
>>>>> org.apache.commons.jelly.JellyTagException:
>>>>> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>>>>>  Type org.eclipse.jgit.transport.RemoteConfig not present
>>>>>
>>>>>
>>>> I think that error means that the git client plugin failed to
>>>> initailize and all git operations after the git client plugin failure to
>>>> initailize will be suspect.  The git client plugin initalization failure is
>>>> likely much earlier in the log file.
>>>>
>>>> Mark Waite
>>>>
>>>>
>>>>
>>>>> Thanks
>>>>> Regards
>>>>>
>>>>> El domingo, 20 de mayo de 2018, 20:21:33 (UTC-3), Mark Waite escribió:
>>>>>
>>>>>> I don't know how the Jenkins loader decides between an hpi and a
>>>>>> jpi file.  I would assume it will choose jpi if it exists, and choose
>>>>>> hpi if the jpi does not exist.  However, that assumption could be
>>>>>> completely wrong.
>>>>>>
>>>>>> The docker image that I use contains only jpi files.  See
>>>>>> https://github.com/MarkEWaite/docker-lfs/tree/lts-slim-with-plugins/ref/plugins
>>>>>>  for
>>>>>> the list of plugins that I use.  I had assumed (possibly incorrectly) 
>>>>>> that
>>>>>> hpi files were originally associated with the Hudson project, and jpi 
>>>>>> files
>>>>>> are associated with the Jenkins project.
>>>>>>
>>>>>> If you have both hpi and jpi files, that may be a source of confusion
>>>>>> for Jenkins.  You might try an experiment to assure that only one or the
>>>>>> other are available.
>>

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

[Mark Waite]

Yes, it means that the git client plugin did not initialize correctly.  The
git client plugin includes JGit.  That class (and the RemoteConfig class)
are classes from JGit which is included in the git client plugin.

On Sun, May 20, 2018 at 6:24 PM Kernel Panic <netwarrior...@gmail.com>
wrote:

> Hi Mark
> Under Manage Old Data I found this, does it mean something to you?
>
> hudson.model.FreeStyleBuild project-name #82 NoClassDefFoundError:
> org/eclipse/jgit/lib/AnyObjectId
> El domingo, 20 de mayo de 2018, 20:36:48 (UTC-3), Mark Waite escribió:
>>
>>
>>
>> On Sun, May 20, 2018 at 5:32 PM Kernel Panic <netwar...@gmail.com> wrote:
>>
>>> Ok, I'll play a bit with it, and what do you think about this error?
>>> does it mean anything? what happens if I remove or clean /var/cache/jenkins
>>> directory? I can bet this is the root of cause, but no idea how to resolve
>>> that
>>> dependency error.
>>>
>>>
>>> org.apache.commons.jelly.JellyTagException:
>>> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>>>  Type org.eclipse.jgit.transport.RemoteConfig not present
>>>
>>>
>> I think that error means that the git client plugin failed to initailize
>> and all git operations after the git client plugin failure to initailize
>> will be suspect.  The git client plugin initalization failure is likely
>> much earlier in the log file.
>>
>> Mark Waite
>>
>>
>>
>>> Thanks
>>> Regards
>>>
>>> El domingo, 20 de mayo de 2018, 20:21:33 (UTC-3), Mark Waite escribió:
>>>
>>>> I don't know how the Jenkins loader decides between an hpi and a
>>>> jpi file.  I would assume it will choose jpi if it exists, and choose
>>>> hpi if the jpi does not exist.  However, that assumption could be
>>>> completely wrong.
>>>>
>>>> The docker image that I use contains only jpi files.  See
>>>> https://github.com/MarkEWaite/docker-lfs/tree/lts-slim-with-plugins/ref/plugins
>>>>  for
>>>> the list of plugins that I use.  I had assumed (possibly incorrectly) that
>>>> hpi files were originally associated with the Hudson project, and jpi files
>>>> are associated with the Jenkins project.
>>>>
>>>> If you have both hpi and jpi files, that may be a source of confusion
>>>> for Jenkins.  You might try an experiment to assure that only one or the
>>>> other are available.
>>>>
>>>> Mark Waite
>>>>
>>>>
>>>>
>>>> On Sun, May 20, 2018 at 5:07 PM Kernel Panic <netwar...@gmail.com>
>>>> wrote:
>>>>
>>> Hi Mark,
>>>>> Yes, that's the output from  /var/log/jenkins/jenkins.log not  of the
>>>>> plugin, and  I get that error on every job I want to configure by the way,
>>>>> is not related to a particular job, are all of them with the same error.
>>>>>
>>>>> Byt the way, I have both jpi and hpi files, which one should I replace
>>>>> with with .bak version?
>>>>>
>>>>>
>>>>> -rw-r--r-- 1 jenkins jenkins 3063466 Oct 30  2015 github.bak
>>>>>
>>>>> -rw-r--r-- 1 jenkins jenkins 3063466 May 17 23:59 github.hpi
>>>>>
>>>>> -rw-r--r-- 1 jenkins jenkins 2421141 May 17 23:40 github.jpi
>>>>>
>>>>>
>>>>>
>>>>> Thanks you very much for your help
>>>>> Regards
>>>>>
>>>>>
>>>>> El domingo, 20 de mayo de 2018, 19:58:43 (UTC-3), Mark Waite escribió:
>>>>>
>>>>>> When I say "the jenkins log", I mean the log file written by Jenkins
>>>>>> as it is running.  I don't mean the log from individual jobs.
>>>>>>
>>>>>> On my Debian machine, the Jenkins logs are written in
>>>>>> /var/log/jenkins/
>>>>>>
>>>>>> Mark Waite
>>>>>>
>>>>>> On Sun, May 20, 2018 at 4:51 PM Kernel Panic <netwar...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>> And this is the full log when I go to project / configure.
>>>>>>>
>>>>>>> org.apache.commons.jelly.JellyTagException: 
>>>>>>> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.je

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

[Mark Waite]

On Sun, May 20, 2018 at 5:32 PM Kernel Panic <netwarrior...@gmail.com>
wrote:

> Ok, I'll play a bit with it, and what do you think about this error? does
> it mean anything? what happens if I remove or clean /var/cache/jenkins
> directory? I can bet this is the root of cause, but no idea how to resolve
> that
> dependency error.
>
>
> org.apache.commons.jelly.JellyTagException:
> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>  Type org.eclipse.jgit.transport.RemoteConfig not present
>
>
I think that error means that the git client plugin failed to initailize
and all git operations after the git client plugin failure to initailize
will be suspect.  The git client plugin initalization failure is likely
much earlier in the log file.

Mark Waite



> Thanks
> Regards
>
> El domingo, 20 de mayo de 2018, 20:21:33 (UTC-3), Mark Waite escribió:
>
>> I don't know how the Jenkins loader decides between an hpi and a
>> jpi file.  I would assume it will choose jpi if it exists, and choose
>> hpi if the jpi does not exist.  However, that assumption could be
>> completely wrong.
>>
>> The docker image that I use contains only jpi files.  See
>> https://github.com/MarkEWaite/docker-lfs/tree/lts-slim-with-plugins/ref/plugins
>>  for
>> the list of plugins that I use.  I had assumed (possibly incorrectly) that
>> hpi files were originally associated with the Hudson project, and jpi files
>> are associated with the Jenkins project.
>>
>> If you have both hpi and jpi files, that may be a source of confusion for
>> Jenkins.  You might try an experiment to assure that only one or the other
>> are available.
>>
>> Mark Waite
>>
>>
>>
>> On Sun, May 20, 2018 at 5:07 PM Kernel Panic <netwar...@gmail.com> wrote:
>>
> Hi Mark,
>>> Yes, that's the output from  /var/log/jenkins/jenkins.log not  of the
>>> plugin, and  I get that error on every job I want to configure by the way,
>>> is not related to a particular job, are all of them with the same error.
>>>
>>> Byt the way, I have both jpi and hpi files, which one should I replace
>>> with with .bak version?
>>>
>>>
>>> -rw-r--r-- 1 jenkins jenkins 3063466 Oct 30  2015 github.bak
>>>
>>> -rw-r--r-- 1 jenkins jenkins 3063466 May 17 23:59 github.hpi
>>>
>>> -rw-r--r-- 1 jenkins jenkins 2421141 May 17 23:40 github.jpi
>>>
>>>
>>>
>>> Thanks you very much for your help
>>> Regards
>>>
>>>
>>> El domingo, 20 de mayo de 2018, 19:58:43 (UTC-3), Mark Waite escribió:
>>>
>>>> When I say "the jenkins log", I mean the log file written by Jenkins as
>>>> it is running.  I don't mean the log from individual jobs.
>>>>
>>>> On my Debian machine, the Jenkins logs are written in /var/log/jenkins/
>>>>
>>>> Mark Waite
>>>>
>>>> On Sun, May 20, 2018 at 4:51 PM Kernel Panic <netwar...@gmail.com>
>>>> wrote:
>>>>
>>> And this is the full log when I go to project / configure.
>>>>>
>>>>> org.apache.commons.jelly.JellyTagException: 
>>>>> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>>>>>   Type org.eclipse.jgit.transport.
>>>>>
>>>>> RemoteConfig not present
>>>>>   at 
>>>>> org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
>>>>>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)
>>>>>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>>>>   at 
>>>>> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>>>>>   at 
>>>>> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>>>>>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>>>>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>>>>   at 
>>>>> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>>>>>   at 
>>>>> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
>>>>>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>>>>   at org.apache.commons.jelly.TagSupport.invokeBody(Tag

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

[Mark Waite]

I don't know how the Jenkins loader decides between an hpi and a jpi file.
I would assume it will choose jpi if it exists, and choose hpi if the
jpi does not exist.  However, that assumption could be completely wrong.

The docker image that I use contains only jpi files.  See
https://github.com/MarkEWaite/docker-lfs/tree/lts-slim-with-plugins/ref/plugins
for
the list of plugins that I use.  I had assumed (possibly incorrectly) that
hpi files were originally associated with the Hudson project, and jpi files
are associated with the Jenkins project.

If you have both hpi and jpi files, that may be a source of confusion for
Jenkins.  You might try an experiment to assure that only one or the other
are available.

Mark Waite



On Sun, May 20, 2018 at 5:07 PM Kernel Panic <netwarrior...@gmail.com>
wrote:

> Hi Mark,
> Yes, that's the output from  /var/log/jenkins/jenkins.log not  of the
> plugin, and  I get that error on every job I want to configure by the way,
> is not related to a particular job, are all of them with the same error.
>
> Byt the way, I have both jpi and hpi files, which one should I replace
> with with .bak version?
>
>
> -rw-r--r-- 1 jenkins jenkins 3063466 Oct 30  2015 github.bak
>
> -rw-r--r-- 1 jenkins jenkins 3063466 May 17 23:59 github.hpi
>
> -rw-r--r-- 1 jenkins jenkins 2421141 May 17 23:40 github.jpi
>
>
>
> Thanks you very much for your help
> Regards
>
>
> El domingo, 20 de mayo de 2018, 19:58:43 (UTC-3), Mark Waite escribió:
>
>> When I say "the jenkins log", I mean the log file written by Jenkins as
>> it is running.  I don't mean the log from individual jobs.
>>
>> On my Debian machine, the Jenkins logs are written in /var/log/jenkins/
>>
>> Mark Waite
>>
>> On Sun, May 20, 2018 at 4:51 PM Kernel Panic <netwar...@gmail.com> wrote:
>>
> And this is the full log when I go to project / configure.
>>>
>>> org.apache.commons.jelly.JellyTagException: 
>>> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>>>   Type org.eclipse.jgit.transport.
>>>
>>> RemoteConfig not present
>>> at 
>>> org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
>>> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)
>>> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>> at 
>>> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>>> at 
>>> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>>> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>> at 
>>> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>>> at 
>>> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
>>> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>> at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
>>> at 
>>> org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
>>> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>> at 
>>> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>>> at 
>>> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>>> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>> at 
>>> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>>> at 
>>> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>>> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>> at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
>>> at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)
>>> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>>> at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
>>> at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
>>> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>>> at org.apache.commons.jelly.impl.ScriptBlock.run(Scrip

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

[Mark Waite]

When I say "the jenkins log", I mean the log file written by Jenkins as it
is running.  I don't mean the log from individual jobs.

On my Debian machine, the Jenkins logs are written in /var/log/jenkins/

Mark Waite

On Sun, May 20, 2018 at 4:51 PM Kernel Panic <netwarrior...@gmail.com>
wrote:

> And this is the full log when I go to project / configure.
>
> org.apache.commons.jelly.JellyTagException: 
> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>   Type org.eclipse.jgit.transport.
>
> RemoteConfig not present
>   at 
> org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at 
> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>   at 
> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at 
> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>   at 
> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
>   at 
> org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>   at 
> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>   at 
> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at 
> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>   at 
> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>   at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
>   at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
>   at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at 
> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>   at 
> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at 
> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>   at 
> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at 
> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>   at 
> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
>   at 
> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>   at 
> org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
>   at 
> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at 
> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>   at 
> org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
>   at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
>   at 
> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
>   at 
> org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
>   at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
>   at org.apache.commons.jelly.impl.ScriptBlock.run(Sc

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

[Mark Waite]

I suspect the last thing in the Jenkins log is much less helpful for
diagnosis than the early contents of the Jenkins log.  Somewhere in the
early portions of the Jenkins log I would expect to find a good hint that
something is unable to start.

On Sun, May 20, 2018 at 4:24 PM Kernel Panic <netwarrior...@gmail.com>
wrote:

> Thank you very much for the explanation, I will try to restore the old
> plugin version, and by the way this is the last thing on jenkins log
>
> Caused by: java.lang.NullPointerException
>
> at
> org.jenkinsci.plugins.github.config.GitHubPluginConfig.constructDefaultUrl(GitHubPluginConfig.java:228)
>
> at
> org.jenkinsci.plugins.github.config.GitHubPluginConfig.getHookUrl(GitHubPluginConfig.java:116)
>
> ... 341 more
>
>
> May 20, 2018 9:00:55 PM hudson.ExpressionFactory2$JexlExpression evaluate
>
> WARNING: Caught exception evaluating: descriptor.helpFile in
> /job/project-name/configure. Reason:
> java.lang.reflect.InvocationTargetException
>
> java.lang.reflect.InvocationTargetException
> at sun.reflect.GeneratedMethodAccessor298.invoke(Unknown Source)Caused
> by: java.lang.NoClassDefFoundError: org/eclipse/jgit/transport/RemoteConfig
>
> at java.lang.Class.getDeclaredMethods0(Native Method)
>
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
>
> at java.lang.Class.getDeclaredMethods(Class.java:1975)
>
> at
> org.kohsuke.stapler.ClassDescriptor.findMethods(ClassDescriptor.java:149)
>
> at org.kohsuke.stapler.ClassDescriptor.(ClassDescriptor.java:85)
>
> at
> org.kohsuke.stapler.lang.KlassNavigator$1.getFunctions(KlassNavigator.java:216)
>
> at
> org.kohsuke.stapler.lang.KlassNavigator$1.getFunctions(KlassNavigator.java:141)
>
> at org.kohsuke.stapler.lang.Klass.getFunctions(Klass.java:98)
>
> at org.kohsuke.stapler.KlassDescriptor.(KlassDescriptor.java:27)
>
> at org.kohsuke.stapler.MetaClass.buildDispatchers(MetaClass.java:105)
>
> at org.kohsuke.stapler.MetaClass.(MetaClass.java:93)
>
> at org.kohsuke.stapler.WebApp.getMetaClass(WebApp.java:204)
>
> at
> org.kohsuke.stapler.jelly.groovy.GroovyFacet.createRequestDispatcher(GroovyFacet.java:109)
>
> at org.kohsuke.stapler.RequestImpl.getView(RequestImpl.java:257)
>
> at org.kohsuke.stapler.RequestImpl.getView(RequestImpl.java:252)
>
> at hudson.model.Descriptor.getHelpFile(Descriptor.java:750)
>
> at hudson.model.Descriptor.getHelpFile(Descriptor.java:732)
>
> at hudson.model.Descriptor.getHelpFile(Descriptor.java:721)
>
> ... 160 more
>
> Caused by: java.lang.ClassNotFoundException:
> org.eclipse.jgit.transport.RemoteConfig
>
> at
> jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1374)
>
> at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1327)
>
> at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1080)
>
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> El domingo, 20 de mayo de 2018, 19:00:03 (UTC-3), Mark Waite escribió:
>
>> On Sun, May 20, 2018 at 2:32 PM Kernel Panic  wrote:
>>
>>> If there was a manual update, ( I can see some some git-client git and
>>> git hub hpi/jpi  files under plugin directory ) how can I revert it back?
>>>
>>> Thanks you very much!
>>>
>>>
>> If one or more plugins were upgraded from a prior version to the current
>> version, then there would be a ".bak" file in the /plugins/
>> subdirectory of the Jenkins home directory.  For example, I recently
>> upgraded the docker-commons plugin and there is now a "docker-commons.bak"
>> file (previous docker-commons plugin version) and a "docker-commons.jpi"
>> file (currentl version of the docker-commons plugin).
>>
>> Plugins which have not been upgraded (at least on my installation) appear
>> as ".jpi" without a matching ".bak".
>>
>> If you want to replace an existing plugin at the file system level with a
>> different version, it may be enough to stop Jenkins, perform a backup, then
>> repalce the ".jpi" (or ".hpi" if it exists
>> instead) with the replacement version.
>>
>> You might also read the Jenkins log file to see if there are hints in the
>> log file that might give an indication why the plugin is unable to start.
>>
>> Mark Waite
>>
>>
>
>>> El domingo, 20 de mayo de 2018, 16:54:48 (UTC-3), Mark Waite escribió:
>>>>
>>>> Have you checked in the "Plugin Manager" section of "Manage Jenkins" to
>>>> confirm that there are no warnings about unsatisfied dependencies?
>>>>
>>>> I think tha

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

[Mark Waite]

On Sun, May 20, 2018 at 2:32 PM Kernel Panic  wrote:

> If there was a manual update, ( I can see some some git-client git and git
> hub hpi/jpi  files under plugin directory ) how can I revert it back?
>
> Thanks you very much!
>
>
If one or more plugins were upgraded from a prior version to the current
version, then there would be a ".bak" file in the /plugins/
subdirectory of the Jenkins home directory.  For example, I recently
upgraded the docker-commons plugin and there is now a "docker-commons.bak"
file (previous docker-commons plugin version) and a "docker-commons.jpi"
file (currentl version of the docker-commons plugin).

Plugins which have not been upgraded (at least on my installation) appear
as ".jpi" without a matching ".bak".

If you want to replace an existing plugin at the file system level with a
different version, it may be enough to stop Jenkins, perform a backup, then
repalce the ".jpi" (or ".hpi" if it exists
instead) with the replacement version.

You might also read the Jenkins log file to see if there are hints in the
log file that might give an indication why the plugin is unable to start.

Mark Waite


>
> El domingo, 20 de mayo de 2018, 16:54:48 (UTC-3), Mark Waite escribió:
>>
>> Have you checked in the "Plugin Manager" section of "Manage Jenkins" to
>> confirm that there are no warnings about unsatisfied dependencies?
>>
>> I think that type of message might appear if a new git plugin were
>> manually uploaded to a system that hadn't yet updated the git client plugin
>> to the latest version.
>>
>> On Sun, May 20, 2018 at 1:50 PM Kernel Panic <netwar...@gmail.com> wrote:
>>
>>> Hello
>>> I inherited a server with git 2.107.3 installed, it seems the previous
>>> admin upgraded it, now when I got to project config I get this error:
>>>
>>> org.apache.commons.jelly.JellyTagException:
>>> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>>>  Type org.eclipse.jgit.transport.RemoteConfig not present
>>>
>>> If I scroll down to Source Management I do not see the git option, only
>>> None, CVS, and CVS Project set.
>>> If I got to Manage Jenkins / Configure System I get the same java error.
>>>
>>> The git plugin version is 3.9.0 and I do no see an option to downgrade,
>>> so Im lost in here, any  idea how can I troubleshoot this issue?
>>> The servert is Debian 8.2
>>>
>>> Thanks in advance
>>> Regards
>>>
>>> --
>>> 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/44b9093d-75d9-4f3f-9a01-39d953c3a64c%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/44b9093d-75d9-4f3f-9a01-39d953c3a64c%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/1b980dec-bbb8-4c5c-889b-9ca1b1890355%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/1b980dec-bbb8-4c5c-889b-9ca1b1890355%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtHLxKv5xvNq2mHVvv0PPcfe4N0uZThrpACM19zAQPn7CQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

[Mark Waite]

On Sun, May 20, 2018 at 2:30 PM Kernel Panic <netwarrior...@gmail.com>
wrote:

> And this is the error I get when building the project
>
> Building on master in workspace /var/lib/jenkins/jobs/project-name/workspace
> [workspace] $ /bin/sh -xe /tmp/jenkins1514082732430590998.sh
>
>
That message says that you have a shell step (probably in a Freestyle job)
that is executing on the master agent in the workspace
/var/lib/jenkins/jobs/project-name/workspace*. *

+ git checkout master
> fatal: Not a git repository (or any parent up to mount point 
> /var/lib/jenkins/jobs)
> Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
>
>
The 'sh' step is calling command line git with the command "git checkout
master".  Command line git expects to find a git repository in
/var/lib/jenkins/jobs/project-name/workspace. Command line does not see a
git repository in /var/lib/jenkins/jobs/project-name/workspace and thus
fails.

If this is a Freestyle job that was defined to use the git plugin but now
the git plugin is no longer able to be loaded, then that is probably an
expected failure. You'll likely need to fix whatever is preventing the git
plugin from being loaded.

Mark Waite

> Build step 'Execute shell' marked build as failure
> Skipped archiving because build is not successful
> Finished: FAILURE
>
>
>



>
> El domingo, 20 de mayo de 2018, 16:54:48 (UTC-3), Mark Waite escribió:
>>
>> Have you checked in the "Plugin Manager" section of "Manage Jenkins" to
>> confirm that there are no warnings about unsatisfied dependencies?
>>
>> I think that type of message might appear if a new git plugin were
>> manually uploaded to a system that hadn't yet updated the git client plugin
>> to the latest version.
>>
>> On Sun, May 20, 2018 at 1:50 PM Kernel Panic <netwar...@gmail.com> wrote:
>>
>>> Hello
>>> I inherited a server with git 2.107.3 installed, it seems the previous
>>> admin upgraded it, now when I got to project config I get this error:
>>>
>>> org.apache.commons.jelly.JellyTagException:
>>> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>>>  Type org.eclipse.jgit.transport.RemoteConfig not present
>>>
>>> If I scroll down to Source Management I do not see the git option, only
>>> None, CVS, and CVS Project set.
>>> If I got to Manage Jenkins / Configure System I get the same java error.
>>>
>>> The git plugin version is 3.9.0 and I do no see an option to downgrade,
>>> so Im lost in here, any  idea how can I troubleshoot this issue?
>>> The servert is Debian 8.2
>>>
>>> Thanks in advance
>>> Regards
>>>
>>> --
>>> 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/44b9093d-75d9-4f3f-9a01-39d953c3a64c%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/44b9093d-75d9-4f3f-9a01-39d953c3a64c%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/f3a61d48-a4ce-4547-89d3-eb8cb321b05d%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/f3a61d48-a4ce-4547-89d3-eb8cb321b05d%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtG_CPHYFmCWCLVd2efALF7jQB3j89mtamM46NJHGydgtQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins-core-2.107.3 jgit.transport.RemoteConfig not present

[Mark Waite]

Have you checked in the "Plugin Manager" section of "Manage Jenkins" to
confirm that there are no warnings about unsatisfied dependencies?

I think that type of message might appear if a new git plugin were manually
uploaded to a system that hadn't yet updated the git client plugin to the
latest version.

On Sun, May 20, 2018 at 1:50 PM Kernel Panic 
wrote:

> Hello
> I inherited a server with git 2.107.3 installed, it seems the previous
> admin upgraded it, now when I got to project config I get this error:
>
> org.apache.commons.jelly.JellyTagException:
> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91:
>  Type org.eclipse.jgit.transport.RemoteConfig not present
>
> If I scroll down to Source Management I do not see the git option, only
> None, CVS, and CVS Project set.
> If I got to Manage Jenkins / Configure System I get the same java error.
>
> The git plugin version is 3.9.0 and I do no see an option to downgrade, so
> Im lost in here, any  idea how can I troubleshoot this issue?
> The servert is Debian 8.2
>
> Thanks in advance
> Regards
>
> --
> 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/44b9093d-75d9-4f3f-9a01-39d953c3a64c%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/CAO49JtFwQmouQpBmBXxfQuyw%3DZkgzkNRuD2WR7SQfTmJME80RA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: SSH deploy key needed for?

[Mark Waite]

No, ssh keys are not used in http or https.

Mark Waite

On Fri, May 18, 2018 at 3:00 AM Tekk nj <tekknj...@gmail.com> wrote:

> Do I need to use my SSH public key in GitLab as a deploy to make a HTTP
> and HTTPS connection between my Jenkins project and the GitLab repo?
>
> --
> 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/fff96124-35da-466b-84ef-ac8ec0c908a8%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/fff96124-35da-466b-84ef-ac8ec0c908a8%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtErFQXFO%3D-oqgPFUJRu7CPx0xqcKH1M0uwyVBFRi6gmAQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GIT_SSH not working on one of my windows slaves

[Mark Waite]

As far as I know, ssh will need to be in the PATH.

On Mon, May 14, 2018 at 9:59 AM red 888 <fakemailred...@gmail.com> wrote:

> Thanks for all the help/suggestions! Will ssh need to be in the system
> path for GIT_SSH_COMMAND="ssh -vvv" to work? because ssh isnt in the path
>
>
> On Friday, May 11, 2018 at 4:51:28 PM UTC-4, Mark Waite wrote:
>>
>> You may be able to use GIT_SSH_COMMAND="ssh -vvv" as a job parameter or
>> an agent environment variable.  Refer to
>> https://support.cloudbees.com/hc/en-us/articles/115000618372-How-to-trace-git-connections-
>>  for
>> more information
>>
>> On Fri, May 11, 2018 at 1:20 PM red 888 <fakemai...@gmail.com> wrote:
>>
>>> How can I get jenkins to give me more verbose output than just "using
>>> GIT_SSH to set credential"
>>>
>>> I set GIT_CURL_VERBOSE=1 and GIT_TRACE=1 on the node but the output
>>> from jenkins doesnt change at all
>>>
>>> I'd like to know what its setting the environment var to and maybe get
>>> some trace level info too. Is there a git
>>>
>>> On Thursday, May 10, 2018 at 3:27:12 PM UTC-4, Mark Waite wrote:
>>>
>>>> The name of the temporary directory used for the credentials is based
>>>> on either the workspace folder path (with @tmp appended) or the environment
>>>> variables %TEMP% or %TMP%.  If none of those contain a space character,
>>>> then that is not the problem.
>>>>
>>>> The plugin usually wirtes a message when it detects a space character
>>>> in a temporary directory path.  Since you didn't report such a message, I
>>>> assume that is not the issue in this case.
>>>>
>>>> Mark Waite
>>>>
>>>> On Thu, May 10, 2018 at 12:38 PM red 888 <fakemai...@gmail.com> wrote:
>>>>
>>> also, if this is helpful this is the global git config on both slaves:
>>>>>
>>>>> PS C:\Users\Administrator> git config --list
>>>>> core.symlinks=false
>>>>> core.autocrlf=true
>>>>> core.fscache=true
>>>>> color.diff=auto
>>>>> color.status=auto
>>>>> color.branch=auto
>>>>> color.interactive=true
>>>>> help.format=html
>>>>> rebase.autosquash=true
>>>>> http.sslcainfo=C:/Program Files/Git/mingw64/ssl/certs/ca-bundle.crt
>>>>> http.sslbackend=openssl
>>>>> diff.astextplain.textconv=astextplain
>>>>> filter.lfs.clean=git-lfs clean -- %f
>>>>> filter.lfs.smudge=git-lfs smudge -- %f
>>>>> filter.lfs.process=git-lfs filter-process
>>>>> filter.lfs.required=true
>>>>>
>>>>> On Thursday, May 10, 2018 at 2:22:10 PM UTC-4, Mark Waite wrote:
>>>>>
>>>>>> Have you confirmed that the temporary directory on the failing
>>>>>> machine does not include any space characters in its path?  There is a
>>>>>> known problem on Windows that the credential passing technique required 
>>>>>> by
>>>>>> command line git does not allow a space character in the temporary
>>>>>> directory path.
>>>>>>
>>>>>> I assume from the log that the workspace does not include a space
>>>>>> character in its path.  If it does, that could invoke the same problem 
>>>>>> with
>>>>>> command line git authentication on Windows not really liking temporary
>>>>>> paths which contain a space character.
>>>>>>
>>>>>> Mark Waite
>>>>>>
>>>>>> On Thu, May 10, 2018 at 12:17 PM red 888 <fakemai...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>> I can confirm the git ssh key works and has always worked so the creds
>>>>>>> themselves should not be an issue.
>>>>>>>
>>>>>>> git clone fails on both slaves (when run interactively as a logged
>>>>>>> in user). The windows task that runs the jnlp executes as the SYSTEM
>>>>>>> account.
>>>>>>>
>>>>>>> I also made sure to do git config --system --unset
>>>>>>> credential.helper. Any local config that would break this?
>>>>>>>
>>>>>>> The git jenkins plugin should be totally handling all the git cred
>>>>>>> setup stuff, 

Re: GIT_SSH not working on one of my windows slaves

[Mark Waite]

You may be able to use GIT_SSH_COMMAND="ssh -vvv" as a job parameter or an
agent environment variable.  Refer to
https://support.cloudbees.com/hc/en-us/articles/115000618372-How-to-trace-git-connections-
for
more information

On Fri, May 11, 2018 at 1:20 PM red 888 <fakemailred...@gmail.com> wrote:

> How can I get jenkins to give me more verbose output than just "using
> GIT_SSH to set credential"
>
> I set GIT_CURL_VERBOSE=1 and GIT_TRACE=1 on the node but the output from
> jenkins doesnt change at all
>
> I'd like to know what its setting the environment var to and maybe get
> some trace level info too. Is there a git
>
> On Thursday, May 10, 2018 at 3:27:12 PM UTC-4, Mark Waite wrote:
>
>> The name of the temporary directory used for the credentials is based on
>> either the workspace folder path (with @tmp appended) or the environment
>> variables %TEMP% or %TMP%.  If none of those contain a space character,
>> then that is not the problem.
>>
>> The plugin usually wirtes a message when it detects a space character in
>> a temporary directory path.  Since you didn't report such a message, I
>> assume that is not the issue in this case.
>>
>> Mark Waite
>>
>> On Thu, May 10, 2018 at 12:38 PM red 888 <fakemai...@gmail.com> wrote:
>>
> also, if this is helpful this is the global git config on both slaves:
>>>
>>> PS C:\Users\Administrator> git config --list
>>> core.symlinks=false
>>> core.autocrlf=true
>>> core.fscache=true
>>> color.diff=auto
>>> color.status=auto
>>> color.branch=auto
>>> color.interactive=true
>>> help.format=html
>>> rebase.autosquash=true
>>> http.sslcainfo=C:/Program Files/Git/mingw64/ssl/certs/ca-bundle.crt
>>> http.sslbackend=openssl
>>> diff.astextplain.textconv=astextplain
>>> filter.lfs.clean=git-lfs clean -- %f
>>> filter.lfs.smudge=git-lfs smudge -- %f
>>> filter.lfs.process=git-lfs filter-process
>>> filter.lfs.required=true
>>>
>>> On Thursday, May 10, 2018 at 2:22:10 PM UTC-4, Mark Waite wrote:
>>>
>>>> Have you confirmed that the temporary directory on the failing machine
>>>> does not include any space characters in its path?  There is a known
>>>> problem on Windows that the credential passing technique required by
>>>> command line git does not allow a space character in the temporary
>>>> directory path.
>>>>
>>>> I assume from the log that the workspace does not include a space
>>>> character in its path.  If it does, that could invoke the same problem with
>>>> command line git authentication on Windows not really liking temporary
>>>> paths which contain a space character.
>>>>
>>>> Mark Waite
>>>>
>>>> On Thu, May 10, 2018 at 12:17 PM red 888 <fakemai...@gmail.com> wrote:
>>>>
>>> I can confirm the git ssh key works and has always worked so the creds
>>>>> themselves should not be an issue.
>>>>>
>>>>> git clone fails on both slaves (when run interactively as a logged in
>>>>> user). The windows task that runs the jnlp executes as the SYSTEM account.
>>>>>
>>>>> I also made sure to do git config --system --unset credential.helper.
>>>>> Any local config that would break this?
>>>>>
>>>>> The git jenkins plugin should be totally handling all the git cred
>>>>> setup stuff, but maybe someone modified a local config on the broken 
>>>>> slave?
>>>>> the git global config looks identical on both of them
>>>>>
>>>>>
>>>>> On Thursday, May 10, 2018 at 1:58:55 PM UTC-4, Mark Waite wrote:
>>>>>
>>>>>> It could be a "happy accident" that it is working on the first
>>>>>> agent.
>>>>>>
>>>>>> When using a command prompt on the first agent, does `git clone`
>>>>>> allow you to clone without prompting for remote username or password?
>>>>>>
>>>>>> When using a command prompt on the second agent, does it behave the
>>>>>> same as the first agent?
>>>>>>
>>>>>> The login context (~/.ssh/ directory contents, environment variables,
>>>>>> etc.) affect agents which use that login context.  If the agent is 
>>>>>> already
>>>>>> configured to silently authenticate to bitbuc

Re: GIT_SSH not working on one of my windows slaves

[Mark Waite]

The name of the temporary directory used for the credentials is based on
either the workspace folder path (with @tmp appended) or the environment
variables %TEMP% or %TMP%.  If none of those contain a space character,
then that is not the problem.

The plugin usually wirtes a message when it detects a space character in a
temporary directory path.  Since you didn't report such a message, I assume
that is not the issue in this case.

Mark Waite

On Thu, May 10, 2018 at 12:38 PM red 888 <fakemailred...@gmail.com> wrote:

> also, if this is helpful this is the global git config on both slaves:
>
> PS C:\Users\Administrator> git config --list
> core.symlinks=false
> core.autocrlf=true
> core.fscache=true
> color.diff=auto
> color.status=auto
> color.branch=auto
> color.interactive=true
> help.format=html
> rebase.autosquash=true
> http.sslcainfo=C:/Program Files/Git/mingw64/ssl/certs/ca-bundle.crt
> http.sslbackend=openssl
> diff.astextplain.textconv=astextplain
> filter.lfs.clean=git-lfs clean -- %f
> filter.lfs.smudge=git-lfs smudge -- %f
> filter.lfs.process=git-lfs filter-process
> filter.lfs.required=true
>
> On Thursday, May 10, 2018 at 2:22:10 PM UTC-4, Mark Waite wrote:
>
>> Have you confirmed that the temporary directory on the failing machine
>> does not include any space characters in its path?  There is a known
>> problem on Windows that the credential passing technique required by
>> command line git does not allow a space character in the temporary
>> directory path.
>>
>> I assume from the log that the workspace does not include a space
>> character in its path.  If it does, that could invoke the same problem with
>> command line git authentication on Windows not really liking temporary
>> paths which contain a space character.
>>
>> Mark Waite
>>
>> On Thu, May 10, 2018 at 12:17 PM red 888 <fakemai...@gmail.com> wrote:
>>
> I can confirm the git ssh key works and has always worked so the creds
>>> themselves should not be an issue.
>>>
>>> git clone fails on both slaves (when run interactively as a logged in
>>> user). The windows task that runs the jnlp executes as the SYSTEM account.
>>>
>>> I also made sure to do git config --system --unset credential.helper.
>>> Any local config that would break this?
>>>
>>> The git jenkins plugin should be totally handling all the git cred setup
>>> stuff, but maybe someone modified a local config on the broken slave? the
>>> git global config looks identical on both of them
>>>
>>>
>>> On Thursday, May 10, 2018 at 1:58:55 PM UTC-4, Mark Waite wrote:
>>>
>>>> It could be a "happy accident" that it is working on the first agent.
>>>>
>>>> When using a command prompt on the first agent, does `git clone` allow
>>>> you to clone without prompting for remote username or password?
>>>>
>>>> When using a command prompt on the second agent, does it behave the
>>>> same as the first agent?
>>>>
>>>> The login context (~/.ssh/ directory contents, environment variables,
>>>> etc.) affect agents which use that login context.  If the agent is already
>>>> configured to silently authenticate to bitbucket, then incorrect
>>>> credentials in the Jenkins environment are ignored and the repository is
>>>> still retrieved.
>>>>
>>>> Mark Waite
>>>>
>>>> On Thu, May 10, 2018 at 11:44 AM Slide <slide...@gmail.com> wrote:
>>>>
>>> Can you try dumping the environment variables on each node and see if
>>>>> there are any differences?
>>>>>
>>>>> On Thu, May 10, 2018 at 10:42 AM red 888 <fakemai...@gmail.com> wrote:
>>>>>
>>>> Super frustrating because this is working on one of my windows slaves,
>>>>>> but not this one- and I cant find any config differences.
>>>>>>
>>>>>> On the working slave I see this:
>>>>>>
>>>>>>
>>>>>> [Pipeline] checkout
>>>>>> Cloning the remote Git repository
>>>>>> Cloning repository g...@bitbucket.org:myteam/myapp.git
>>>>>>  > git init C:\Jenkins\workspace\test-slave123456 # timeout=10
>>>>>> Fetching upstream changes from g...@bitbucket.org:myteam/myapp.git
>>>>>>  > git --version # timeout=10
>>>>>> using GIT_SSH to set credentials mygitcreds
>>>>>>  > git fetch --tags --progress g...@bi

Re: GIT_SSH not working on one of my windows slaves

[Mark Waite]

Have you confirmed that the temporary directory on the failing machine does
not include any space characters in its path?  There is a known problem on
Windows that the credential passing technique required by command line git
does not allow a space character in the temporary directory path.

I assume from the log that the workspace does not include a space character
in its path.  If it does, that could invoke the same problem with command
line git authentication on Windows not really liking temporary paths which
contain a space character.

Mark Waite

On Thu, May 10, 2018 at 12:17 PM red 888 <fakemailred...@gmail.com> wrote:

> I can confirm the git ssh key works and has always worked so the creds
> themselves should not be an issue.
>
> git clone fails on both slaves (when run interactively as a logged in
> user). The windows task that runs the jnlp executes as the SYSTEM account.
>
> I also made sure to do git config --system --unset credential.helper. Any
> local config that would break this?
>
> The git jenkins plugin should be totally handling all the git cred setup
> stuff, but maybe someone modified a local config on the broken slave? the
> git global config looks identical on both of them
>
>
> On Thursday, May 10, 2018 at 1:58:55 PM UTC-4, Mark Waite wrote:
>
>> It could be a "happy accident" that it is working on the first agent.
>>
>> When using a command prompt on the first agent, does `git clone` allow
>> you to clone without prompting for remote username or password?
>>
>> When using a command prompt on the second agent, does it behave the same
>> as the first agent?
>>
>> The login context (~/.ssh/ directory contents, environment variables,
>> etc.) affect agents which use that login context.  If the agent is already
>> configured to silently authenticate to bitbucket, then incorrect
>> credentials in the Jenkins environment are ignored and the repository is
>> still retrieved.
>>
>> Mark Waite
>>
>> On Thu, May 10, 2018 at 11:44 AM Slide <slide...@gmail.com> wrote:
>>
> Can you try dumping the environment variables on each node and see if
>>> there are any differences?
>>>
>>> On Thu, May 10, 2018 at 10:42 AM red 888 <fakemai...@gmail.com> wrote:
>>>
>> Super frustrating because this is working on one of my windows slaves,
>>>> but not this one- and I cant find any config differences.
>>>>
>>>> On the working slave I see this:
>>>>
>>>>
>>>> [Pipeline] checkout
>>>> Cloning the remote Git repository
>>>> Cloning repository g...@bitbucket.org:myteam/myapp.git
>>>>  > git init C:\Jenkins\workspace\test-slave123456 # timeout=10
>>>> Fetching upstream changes from g...@bitbucket.org:myteam/myapp.git
>>>>  > git --version # timeout=10
>>>> using GIT_SSH to set credentials mygitcreds
>>>>  > git fetch --tags --progress g...@bitbucket.org:myteam/myapp.git 
>>>> +refs/heads/*:refs/remotes/origin/* # timeout=45
>>>>  > git config remote.origin.url g...@bitbucket.org:myteam/myapp.git # 
>>>> timeout=10
>>>>  > git config --add remote.origin.fetch 
>>>> +refs/heads/*:refs/remotes/origin/* # timeout=10
>>>>  > git config remote.origin.url g...@bitbucket.org:myteam/myapp.git # 
>>>> timeout=10
>>>> Fetching upstream changes from g...@bitbucket.org:myteam/myapp.git
>>>> using GIT_SSH to set credentials mygitcreds
>>>>  > git fetch --tags --progress g...@bitbucket.org:myteam/myapp.git 
>>>> +refs/heads/*:refs/remotes/origin/* # timeout=45
>>>>  > git rev-parse "origin/test-slave^{commit}" # timeout=10
>>>> Checking out Revision 30f11ef09ab13f73fb9a6b75983e1bf32437f51d 
>>>> (origin/test-slave)
>>>> Enabling Git LFS pull
>>>>  > git config core.sparsecheckout # timeout=10
>>>>  > git checkout -f 30f11ef09ab13f73fb9a6b75983e1bf32437f51d # timeout=45
>>>>  > git config --get remote.origin.url # timeout=10
>>>> using GIT_SSH to set credentials mygitcreds
>>>>  > git lfs pull origin # timeout=45
>>>> Commit message: "test slave"
>>>>  > git rev-list --no-walk 30f11ef09ab13f73fb9a6b75983e1bf32437f51d # 
>>>> timeout=10
>>>>
>>>>
>>>>
>>>> But on the failing slave:
>>>>
>>>>
>>>> [Pipeline] checkout
>>>> Cloning the remote Git repository
>>>> Cloning repository g...@bitbucket.org:m

Re: GIT_SSH not working on one of my windows slaves

[Mark Waite]

It could be a "happy accident" that it is working on the first agent.

When using a command prompt on the first agent, does `git clone` allow you
to clone without prompting for remote username or password?

When using a command prompt on the second agent, does it behave the same as
the first agent?

The login context (~/.ssh/ directory contents, environment variables, etc.)
affect agents which use that login context.  If the agent is already
configured to silently authenticate to bitbucket, then incorrect
credentials in the Jenkins environment are ignored and the repository is
still retrieved.

Mark Waite

On Thu, May 10, 2018 at 11:44 AM Slide <slide.o@gmail.com> wrote:

> Can you try dumping the environment variables on each node and see if
> there are any differences?
>
> On Thu, May 10, 2018 at 10:42 AM red 888 <fakemailred...@gmail.com> wrote:
>
>> Super frustrating because this is working on one of my windows slaves,
>> but not this one- and I cant find any config differences.
>>
>> On the working slave I see this:
>>
>>
>> [Pipeline] checkout
>> Cloning the remote Git repository
>> Cloning repository g...@bitbucket.org:myteam/myapp.git
>>  > git init C:\Jenkins\workspace\test-slave123456 # timeout=10
>> Fetching upstream changes from g...@bitbucket.org:myteam/myapp.git
>>  > git --version # timeout=10
>> using GIT_SSH to set credentials mygitcreds
>>  > git fetch --tags --progress g...@bitbucket.org:myteam/myapp.git 
>> +refs/heads/*:refs/remotes/origin/* # timeout=45
>>  > git config remote.origin.url g...@bitbucket.org:myteam/myapp.git # 
>> timeout=10
>>  > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* 
>> # timeout=10
>>  > git config remote.origin.url g...@bitbucket.org:myteam/myapp.git # 
>> timeout=10
>> Fetching upstream changes from g...@bitbucket.org:myteam/myapp.git
>> using GIT_SSH to set credentials mygitcreds
>>  > git fetch --tags --progress g...@bitbucket.org:myteam/myapp.git 
>> +refs/heads/*:refs/remotes/origin/* # timeout=45
>>  > git rev-parse "origin/test-slave^{commit}" # timeout=10
>> Checking out Revision 30f11ef09ab13f73fb9a6b75983e1bf32437f51d 
>> (origin/test-slave)
>> Enabling Git LFS pull
>>  > git config core.sparsecheckout # timeout=10
>>  > git checkout -f 30f11ef09ab13f73fb9a6b75983e1bf32437f51d # timeout=45
>>  > git config --get remote.origin.url # timeout=10
>> using GIT_SSH to set credentials mygitcreds
>>  > git lfs pull origin # timeout=45
>> Commit message: "test slave"
>>  > git rev-list --no-walk 30f11ef09ab13f73fb9a6b75983e1bf32437f51d # 
>> timeout=10
>>
>>
>>
>> But on the failing slave:
>>
>>
>> [Pipeline] checkout
>> Cloning the remote Git repository
>> Cloning repository g...@bitbucket.org:myteam/myapp.git
>>  > git init C:\Jenkins\workspace\test-slave123456 # timeout=10
>> Fetching upstream changes from g...@bitbucket.org:myteam/myapp.git
>>  > git --version # timeout=10
>> using GIT_SSH to set credentials mygitcreds
>>  > git fetch --tags --progress g...@bitbucket.org:myteam/myapp.git 
>> +refs/heads/*:refs/remotes/origin/* # timeout=45
>> ERROR: Error cloning remote repo 'origin'
>> hudson.plugins.git.GitException: Command "git fetch --tags --progress 
>> g...@bitbucket.org:myteam/myapp.git +refs/heads/*:refs/remotes/origin/*" 
>> returned status code 128:
>> stdout:
>> stderr: gituserfromcredbind...@bitbucket.org: Permission denied (publickey).
>> fatal: Could not read from remote repository.
>>
>>
>> Its the same pipeline job, same repo, same creds, and the slave should be
>> configured the same but when I change the agent to point to the other slave
>> it cant clone.
>>
>>
>> On the working slave all i had to do was install git for windows (turn
>> off windows cred store), install java, and then run the jnlp jar.
>>
>>
>> Tried to do the same thing on the non working slave so I dont know why
>> that one could be failing.
>>
>> --
>> 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/3afe4362-20f7-40c9-91ac-ac6573d0bd16%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/3afe4362-20f7-40c9-91ac-ac657

Re: java.io.IOException: Cannot run program "chmod": java.io.IOException

[Mark Waite]

Are you running on Windows?  There is no chmod on windows.  The Windows
file system permission system is different than the Unix file system
permission system.

If you're running on a Unix variant (Linux, macOS, FreeBSD, Solaris,
AIX, OpenBSD, hp-ux, etc.), is the chmod command in the PATH of the ant
process?

Mark Waite

On Mon, May 7, 2018 at 5:04 AM Ganesh MN <ganesh.ujjanip...@gmail.com>
wrote:

>
> Hi,
>
> I am running ant task to change permission of files form Jenkins tool.
> But, I am getting following exception.
> Can someone please help me to resolve this issue.  Waiting to here form
> you guys.
>
> ant task:
>
>
> 
> 
> 
>  
>   
> 
> 
>
>
> console output:
>
> Execute failed: java.io.IOException: Cannot run program "chmod": 
> java.io.IOException: error=2, No such file or directory*16:26:24*at 
> org.apache.tools.ant.taskdefs.Chmod.execute(Chmod.java:183)*16:26:24*
> at 
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)*16:26:24*
>at org.apache.tools.ant.Task.perform(Task.java:364)*16:26:24*   at 
> org.apache.tools.ant.Target.execute(Target.java:341)*16:26:24*   at 
> org.apache.tools.ant.Target.performTasks(Target.java:369)*16:26:24*  at 
> org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)*16:26:24*
>at 
> org.apache.tools.ant.Project.executeTarget(Project.java:1185)*16:26:24*  
> at 
> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)*16:26:24*
> at 
> org.apache.tools.ant.Project.executeTargets(Project.java:1068)*16:26:24* 
> at org.apache.tools.ant.Main.runBuild(Main.java:668)*16:26:24*  at 
> org.apache.tools.ant.Main.startAnt(Main.java:187)*16:26:24*  at 
> org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)*16:26:24*
> at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
>
>
>
>
> Thanks,
>
> Ganesha
>
> --
> 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/24a9930d-3751-4b20-a026-25d5fc1a9a98%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/24a9930d-3751-4b20-a026-25d5fc1a9a98%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFzcYw9LE5xLEueuKKyq-uo7mENttbyHFKDW7CCopSt0A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.