On Tue, Jun 11, 2019 at 4:53 PM Giles wrote:
> Unfortunately, I appear to have gone from the frying pan to the fire. I
> ran one deploy that hadn't worked previously and it did work, and I
> immediately responded with an "it's working" message. And that single
> deploy still works. But
Unfortunately, I appear to have gone from the frying pan to the fire. I
ran one deploy that hadn't worked previously and it did work, and I
immediately responded with an "it's working" message. And that single
deploy still works. But multiple others (all based on the same code, with
only
On Tue, Jun 11, 2019 at 1:47 PM Guy Knights wrote:
> I've been looking into multibranch pipeline and I'm wondering, can it be
> configured to support build parameters to specify which branches will be
> built?
>
> I know the branch config can be setup with a regex to specify that certain
>
I'm glad that helped. In the past, we've seen cases where a new version of
ssh surprises the credential integration that is used by the git plugin. I
don't think your case is related to that, but I did see that Git for
Windows 2.22.0 now includes OpenSSH 8.0. I need to add that version into
my
Nailed it in one.
I was sure it was a Jenkins issue ... but I'd upgraded Cygwin at the same
time, and that probably included their version of git. Which yes, is my
default git. I changed "Manage Jenkins" -> "Global Tool Configuration" ->
git to the just-installed "Git for Windows", and ...
I've been looking into multibranch pipeline and I'm wondering, can it be
configured to support build parameters to specify which branches will be
built?
I know the branch config can be setup with a regex to specify that certain
branches will be built, but it means that the same branches will be
Tried that too. No go. I found other blogs about the same thing and the
answer seems to be use batch commands. Those blogs were for old revisions
so I figured that perhaps this was fixed by now. Perhaps it was fixed some
time ago and is now broke again.
On Tuesday, June 11, 2019 at 9:17:00
Are you quite sure that your configuration did not change in about the same
time as that upgrade?
The log file indicates that you're running command line git as provided by
Cygwin. Is that intentional? Has it always been that way?
I don't test the Jenkins git plugin with Cygwin. I test with
Hi Panneer,
I guess you can make use of api provided by jenkins to get above details
regarding build. You can try below link to know how to fetch details from
jenkins api.
https://github.com/jenkinsci/pipeline-stage-view-plugin/blob/master/rest-api/README.md
On Tue, Jun 11, 2019, 5:31 AM
I'm running Jenkins 2.164.3 on a Windows server. It's been running well
for several months. Every Friday evening I do all the Jenkins plugin
updates. After this past Friday's updates (details below), all our jobs
are broken - apparently because the GitSCM checkout is broken. Our
I have an unsolved annoying issue regarding Jenkins pipelines and Docker
Content Trust, I hope someone can give me a hand with it.
I'm using Harbor as private registry and I activated Content Trust on my
laptop's Docker daemon. Whenever I push a new Image to the registry
manually from the
You could copy the files into the workspace from the location they are
currently in. Most Jenkins plugins will only act on things under the
workspace for good reasons (security for one).
On Tue, Jun 11, 2019 at 7:13 AM Nef Rey wrote:
> That would be a bummer... The files that I need to access
That would be a bummer... The files that I need to access are not in the
workspace (its complicated). They are moved to another folder. I'm using
the batch command for now, but wish I could use the plugin.
On Tuesday, June 11, 2019 at 3:52:53 AM UTC-5, Richard Bywater wrote:
>
> Pure guess
Upgraded to 1.20 and I got the same error.
Sigh, wish they could actually get the syntax set once and for all.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
Hi, this matches my config which looks like this:
- certificate:
id: "our-keystore"
description: "certificate-alias"
keyStoreSource:
fileOnMaster:
keyStoreFile:
This matches my configuration except that I had to add the alias of the
certificate as "description". Not sure if that was the error I got though.
Eveything else matches my config.
/Andreas
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To
Inherited project with little documentation and less experience with
actually managing ant builds.
My understanding is that build.xml can get its property values from a file
called build.propoerties.
My problem is: I cannot find "build.properities" anywhere in the project
code nor on the
I have the following Pipeline step to find specific files:
sh("find . -regex '.*${packageName}-[0-9.]+-.\\.noarch\\.rpm'")
The Output:
[Pipeline] sh
+ find . -regex '.*package-name-[0-9.]+-.\.noarch\.rpm'
This does not return any result.
Both of these two works in Bash:
find . -regex
Pure guess without looking at the plugin code or ever having used the
plugin but I'm guessing Test Files need to be specified as a relative path
within the workspace rather than an arbitrary file somewhere else on the
disk.
Richard.
On Tue, 11 Jun 2019 at 05:13, Nef Rey wrote:
> I'm using a
19 matches
Mail list logo
