Re: Not able to access and create files in path location(\\\\192.168.0.1/f$/D:\\p.txt)

Hi, There are a few things which could be the reason ( and your descriptions are a bit too sparse to guess what is). 1) Is jenkins running on your local host? (only then the 192 probably resolve to a correct host) if not: 2) is the job running on master or on an agent ( again, the 1

Re: Not able to access and create files in path location(\\\\192.168.0.1/f$/D:\\p.txt)

thats fine. Its creating the file in local. For ex:shared path(192.168.0.1\\foldername\\p.txt) while executing the program through eclipse its working and creating the filse in shared path. if iam running through jenkins its not creating. we are using active directory Authenticator. Not the J

Re: Not able to access and create files in pathlocation(\\\\192.168.0.1/f$/D:\\p.txt)

we are using active directory Authenticator. Not the Jenkins user. On Tue, Sep 25, 2018, 10:36 PM Slide wrote: > [image: Boxbe] This message is eligible > for Automatic Cleanup! (slide.o@gmail.com) Add cleanup rule >

Re: Configuration as code and preservation of credentials

> Am 25.09.2018 um 22:27 schrieb nicolas de loof : > > A feature we'd like to investigate for JCasC is to make the web UI read-only > once configured from yaml > The specific sample of credentials could be adapted to support "preserve > existing entries" but we have no way to support this in a

Re: Configuration as code and preservation of credentials

Hi Nicolas, Thanks for your feedback. In our case, we're using CasC to maintain and push known and tested versions of a Jenkins master into a production environment, but we wanted to still accept some degree of freedom, esp. when it comes to credential management. An alternative is to use an ext

Re: Configuration as code and preservation of credentials

A feature we'd like to investigate for JCasC is to make the web UI read-only once configured from yaml The specific sample of credentials could be adapted to support "preserve existing entries" but we have no way to support this in a generic way Also, JCasC is designed to support re-creating an equ

Re: Agent on Tandem/NonStop: sh pipeline command yields nohup error, while plain shell script build step works

I have solved this (for now) by executing ~/.bashrc as a prefix on the slave startup command (hack hack hack -- nasty cough). This has the effect of setting the PATH variable to have /usr/coreutils/bin in front of /bin. I am still confused about why the shell running the ssh agent shows itself

Re: Configuration as code and preservation of credentials

But many things are otherwise preserved. I feel the implementation of the credentials configuration is doing a none vs. all approach, not taking into account existing entries: In SystemCredentialsProviderConfigurator: target.setDomainCredentialsMap(DomainCredentials.asMap(value)) Maybe this c

Re: Configuration as code and preservation of credentials

I've created the PR at https://github.com/jenkinsci/configuration-as-code-plugin/pull/556 to show an unit test reproducing the issue. On Tuesday, September 25, 2018 at 9:04:31 PM UTC+2, damien.c...@collibra.com wrote: > > Hi, > > We're using Jenkins 2.121.3 and CasC 1.0. One thing we define as

Re: Configuration as code and preservation of credentials

This is one of the drawbacks of JCasC of the current version. You can’t change anything in the UI anymore if you enable JCasC. Everything will be lost after restart. It would make sense to have a way to use both JCasC and the manual UI configuration together somehow. > Am 25.09.2018 um 21:04 sch

Windows 10 node and ssh-slave plugin

Hello, I would like to know if the ssh-slave plugin is supposed to work to run the slave agent on a Windows 10 node with Open SSH (Microsoft port)? I tried but I got some issues: 1/ the plugin assumes a command named *true* exists for the shell being executed (ok for bash but not for cmd, the sh

Re: Agent on Tandem/NonStop: sh pipeline command yields nohup error, while plain shell script build step works

Here's some more fun stuff...the Jenkins agent is started via SSH. So, using SSH from the jenkins account on the RHEL box (same account that jenkins is running under (jenkins): jenkins@bmc053:~$ ssh m...@tsek.atc-hpe.com 'type nohup' nohup is /bin/nohup jenkins@bmc053:~$ ssh m...@tsek.atc-hpe.c

Re: Agent on Tandem/NonStop: sh pipeline command yields nohup error, while plain shell script build step works

The agent may be running /bin/sh. I suspect this because of the agent log, which contains the following: [09/25/18 12:17:49] [SSH] Opening SSH connection to tsek.atc-hpe.com:22. [09/25/18 12:17:49] [SSH] SSH host key matches key in Known Hosts file. Connection will be allowed. ERROR: Server rej

Configuration as code and preservation of credentials

Hi, We're using Jenkins 2.121.3 and CasC 1.0. One thing we define as code is a list of credentials (some SSH keys, some user/passwords, etc.) common to all our instances but we let also the administrators of a Jenkins instance define their own credential entries. However, when the Jenkins inst

Re: Agent on Tandem/NonStop: sh pipeline command yields nohup error, while plain shell script build step works

Is it possible that the /bin at the front of PATH is causing ksh instead of bash to be used when you run sh? I think nohup is a builtin in ksh so would get 4002 when forkAndExec is called across the pipe? On Tuesday, September 25, 2018 at 2:53:12 PM UTC-4, Meg Watson wrote: > > I am using bash,

Re: Agent on Tandem/NonStop: sh pipeline command yields nohup error, while plain shell script build step works

I am using bash, afaik. And I have used local pipelines without issue as well. It seems to be related to the agent process. If I send the agent a job (non-pipeline) with the following shell commands env whoami gtacl -c sysinfo nohup --help ...here is the output: Started by user mwatson

Re: Still Login Problem.

Ya IT WORKED for the first time. Thanx for allowing me, for the first time, to escape the login page. On Tue, Sep 25, 2018 at 1:03 PM Slide wrote: > Based on this line from your log: > > Jenkins home directory: C:\Users\sburris125\.jenkins found at: > $user.home/.jenkins > > Please try following

Re: Agent on Tandem/NonStop: sh pipeline command yields nohup error, while plain shell script build step works

On Tuesday, September 25, 2018 at 1:37:54 PM UTC-4, Devin Nusbaum wrote: > > The `sh` step in a Jenkins Pipeline uses `nohup` to launch the script on > the agent in such a way that Jenkins can restart while the `sh` step is > running without interrupting the script’s execution. > > Is the `nohup

Re: Still Login Problem.

Based on this line from your log: Jenkins home directory: C:\Users\sburris125\.jenkins found at: $user.home/.jenkins Please try following these steps (again I know) using C:\Users\sburris125\.jenkins as $JENKINS_HOME https://jenkins.io/doc/book/system-administration/security/#disabling-security

Re: Agent on Tandem/NonStop: sh pipeline command yields nohup error, while plain shell script build step works

The `sh` step in a Jenkins Pipeline uses `nohup` to launch the script on the agent in such a way that Jenkins can restart while the `sh` step is running without interrupting the script’s execution. Is the `nohup` command available on NonStop/Tandem machines? If so, is it reachable from the agen

Re: downgraded to 2.73.3 from 2.121.3 but plugins not yet

Then difficult to find out the compatibility of the pluigins with the Downgraded Jenkins. On Tuesday, September 25, 2018 at 10:07:33 PM UTC+5:30, slide wrote: > > Plugins will not downgrade just because you downgraded Jenkins itself. > > On Tue, Sep 25, 2018 at 9:31 AM > wrote: > >> Hi, >> >> Ev

Re: Still Login Problem.

No it was actiually in th e C:\MyJenkins folder from which I deleted the config.xml file. On Tue, Sep 25, 2018 at 10:33 AM Slide wrote: > Hi Steve, > > Just to make sure, the config.xml file you edited to remove the security > is C:\Users\sburris125\.jenkins\config.xml, correct? > > Thanks, >

Re: Not able to access and create files in pathlocation(\\\\192.168.0.1/f$/D:\\p.txt)

Sounds like your Jenkins is running as a different user that doesn't have permissions to write to that share. On Tue, Sep 25, 2018 at 9:32 AM Saikumar Korada wrote: > Hi one more clarification. > Re: Not able to access and create files in > pathlocation(192.168.0.1\\screenshots\\p.txt) Share

Re: downgraded to 2.73.3 from 2.121.3 but plugins not yet

Plugins will not downgrade just because you downgraded Jenkins itself. On Tue, Sep 25, 2018 at 9:31 AM wrote: > Hi, > > Even though Jenkin version is downgraded to 2.73.3 from 2.121.3 the Plugin > versions still referring to the same version > Installed plugins not yet downgraded infact no optio

Re: Not able to access and create files in pathlocation(\\\\192.168.0.1/f$/D:\\p.txt)

Hi one more clarification. Re: Not able to access and create files in pathlocation(192.168.0.1\\screenshots\\p.txt) Shared folder parh. while executing the program through eclipse its working. if iam running through jenkins its not working. On Mon, Sep 24, 2018, 4:29 PM Andreas Magnusson < and

downgraded to 2.73.3 from 2.121.3 but plugins not yet

Hi, Even though Jenkin version is downgraded to 2.73.3 from 2.121.3 the Plugin versions still referring to the same version Installed plugins not yet downgraded infact no option to downgrade also. Artifactory Plugin version : 2.16.2 and Kubernetes : 1.8.4 Looks like some thing more need to b

Re: SAML plugin with SSO

Hi, Did you read the documentation at https://github.com/jenkinsci/saml-plugin/tree/master/doc? you should take a look at the troubleshooting guide. The probable cause, it is that you do not set the proper group and display name for your IdP, Jenkins do not know anything about your IdP and dif

Agent on Tandem/NonStop: sh pipeline command yields nohup error, while plain shell script build step works

Hi, I'm a newbie to pipelines. I have a Jenkins master running on Linux (RHEL), and I have an agent running (via SSH) on a NonStop/Tandem machine, which looks like UNIX for all intents and purposes. I can run various jobs on the NonStop agent without issue, build steps with shell commands wor

Re: Still Login Problem.

Hi Steve, Just to make sure, the config.xml file you edited to remove the security is C:\Users\sburris125\.jenkins\config.xml, correct? Thanks, Alex On Tue, Sep 25, 2018 at 8:25 AM Steve Burrus wrote: > Okay careful what you ask for. Here is the "dump" from my Jenkimns command > prompt : > >

Re: Still Login Problem.

Okay careful what you ask for. Here is the "dump" from my Jenkimns command prompt : C:\MyJenkins>java -jar jenkins.war --httpPort=8032 Running from: C:\MyJenkins\jenkins.war webroot: $user.home/.jenkins Sep 25, 2018 10:03:52 AM org.eclipse.jetty.util.log.Log initialized INFO: Logging initialized @

Re: Install wildcars ssl certs in opensource Jenkins ver. 2.121

Hi, See https://wiki.jenkins.io/display/JENKINS/Starting+and+Accessing+Jenkins *> Using HTTPS with an existing certificate* If you still can't achieve it, please post more details about what you have tried, and how it failed, so that we can help. Regarding your message, Please suggest the ste

Install wildcars ssl certs in opensource Jenkins ver. 2.121

I have open source Jenkins installed and people get authenticated using AD. Currently it works on http://$URL.com. Need to install wild card certs to make it https://$URL.com. Please suggest the steps. Went through this page https://wiki.jenkins.io/pages/viewpage.action?pageId=135468777, bu

Re: Still Login Problem.

See https://jenkins.io/doc/book/system-administration/security/#disabling-security Steve, please generally be more precise with what you've tried, the errors you see and everything. This is required to be able to help you. Most of the times, a one-liner is not enough and you can provide much more

Re: SAML plugin with SSO

Multi-posting probably will not help you get help on your issue. People on the list have seen it, it may take some time to get a response. On Tue, Sep 25, 2018 at 5:41 AM Prasu S wrote: > On Monday, September 24, 2018 at 2:07:12 PM UTC-4, Prasu S wrote: > > Hi , > > > > > > We are planning to im

Re: SAML plugin with SSO

On Monday, September 24, 2018 at 2:07:12 PM UTC-4, Prasu S wrote: > Hi , > > > We are planning to implement MFA(multi factor authentication) for Jenkins > 2.138 . I installed SAML plugin 1.0.7 and configured it with IDP metadata > provided by service provider.Display Name attribute and group at