Title: Re: different github checkout revisions
Thanks for your reply.
Temporarily, I have to roll back to the old, but working successfully solution with git:
git(
url: 'https://github.com/enterpr/myrepo.git',
credentialsId: 'github-PAT',
branch: "${params.branch_name}"
some way to restrict User1 to trigger the build button from console on
master branch?
On Wed, Dec 2, 2020 at 2:03 AM Jibsan Joel Rosa Toirac
wrote:
> Well I solved the problem, I used "sudo" before the commands and it
> started to work, anyhow I ran the command
> "root/.sdkman/candidates/grails
We have too many tests, so we have broken them up into three groups. One
group that runs after each checkin and one group that runs once a day on
any branch with changes and one group that I would like to limit to one
instance at a time but still test any active branch.
What is the best way to
Well I solved the problem, I used "sudo" before the commands and it started
to work, anyhow I ran the command
"root/.sdkman/candidates/grails/3.3.2/bin/grails war" and all started to
work. Thanks for your help
El mar, 1 dic 2020 a las 10:30, Rishi Gautam ()
escribió:
> Is there any way to enable
Is there any way to enable authorization to build only specific
branch(job) on jenkins multbranch pipeline?
Use Case:
User1: can only build test branch.
User2: can build both test and master branch.
It would be very helpful to get the solution. Thanks in advance.
--
You received this message b
On Tue, Dec 1, 2020 at 5:32 AM wrote:
> There is such a jenkins-code:
>
> checkout ([ ...
> extensions: [[$class: 'CheckoutOption', timeout: 180],[$class:
> 'CloneOption', depth: 1, noTags: true, reference: '', shallow: false,
> timeout: 60]],
> ... )]
>
> Why do I get different revisions when I
There is such a jenkins-code:
checkout ([ ...
extensions: [[$class: 'CheckoutOption', timeout: 180],[$class: 'CloneOption',
depth: 1, noTags: true, reference: '', shallow: false, timeout: 60]],
... )]
Why do I get different revisions when I restart the same pipeline, without any
changes in SCM
Hello Team,
I have been trying to implement the functionality of having default Admin
API token at the time of deployment of Jenkins. I have been following the
below link.
https://github.com/jenkinsci/jenkins/pull/4027/commits
As per the instruction, I have setup the system properties with fix
Hello Team,
As per the link : https://github.com/jenkinsci/jenkins/pull/4027
Which says that there would be new API feature :
"Provide a way to configure a fixed/default API Token for admin during
installation phase"
I have been trying to implement this with Jenkins version "2.26`" using
helm c
