munged workspace folder names?

Is this a feature of Jenkins where it appears to munge the job name when generating the folder name under workspace? Does this apply to GitHub organization jobs only? I show where the folder name under itbox/workspaces on my slave is missing the first character of the job name. and earlier I c

Problems upgrading from 2.263 to 2346.2

Currently I see this in the system log It appears whenever you look at a job from the dashboard and it needs to show it’s build history. Kind of puzzling why this happens for some jobs and not others. The jobs appear under a Folder. java.lang.NoSuchMethodError: com.google

Re: Tagging code in a pipeline?

te > wrote: >> >> Is the repository URL an ssh URL? If not, then sshagent won't help. The >> ssh agent does not do http or https >> >> On Thu, Mar 21, 2019 at 12:51 PM Robert Nicholson > >> wrote: >> I am able to tag the code locally but the p

Re: GIT_SSH having no effect

hy not use the sshagent step instead of using > withCredentials? > > On Fri, Mar 22, 2019 at 3:17 PM Robert Nicholson <mailto:robert.nichol...@gmail.com>> wrote: > When I try to use > > withCredentials() > withEnv(‘GIT_SSH=doesnotexist’]) >

GIT_SSH having no effect

When I try to use withCredentials() withEnv(‘GIT_SSH=doesnotexist’]) sh ‘git push origin —tags’ For some reason the GIT_SSH seems to have no effect whatever. The git push doesn’t complain that way I would have expected But if I use withEnv(‘PATH=‘]) sh ‘git push o

Re: Tagging code in a pipeline?

> agent does not do http or https > > On Thu, Mar 21, 2019 at 12:51 PM Robert Nicholson <mailto:robert.nichol...@gmail.com>> wrote: > I am able to tag the code locally but the push with credentials key based > seems to be an issue. > > sshagent([‘credentialsK

Tagging code in a pipeline?

I am able to tag the code locally but the push with credentials key based seems to be an issue. sshagent([‘credentialsKey]) { sh “git push origin master —tags” } this step errors with fatal: could not read Username for ‘repository hostname’ : No such device or address Prior in my pipeline

Jenkins meta data plugin not always showing the latest versions?

I’m using the plugin the plugin that says “List maven artifact versions” and I’m noticing that often it’s not always up to date in the versions it’s offering and I can see that maven-metadata.xml does include more recent versions. Even when I can clearly see my maven repository is showing more r

Active Choices Plugin populated via ssh?

Can Active Choices Plugin support populating itself using ssh or can it only read a flat file? -- You received this message because you are 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+