Maybe I didn't describe it clearly. When I use Jenkins, I find that the
effect of selecting 'all' and 'compatibility' in 'plugins manager' is the
same, I want to know how to distinguish between compatible plugins.
On Wednesday, November 27, 2019 at 1:38:55 PM UTC+8, YanJun Shi wrote:
>
> Hi,
>
I think your question is better suited for the users list.
> Am 03.12.2019 um 03:31 schrieb YanJun Shi :
>
> Maybe I didn't describe it clearly. When I use Jenkins, I find that the
> effect of selecting 'all' and 'compatibility' in 'plugins manager' is the
> same, I want to know how to
okay. I'll send that to the users list. Thanks.
On Tue, Dec 3, 2019 at 2:25 PM Ullrich Hafner
wrote:
> I think your question is better suited for the users list.
>
> Am 03.12.2019 um 03:31 schrieb YanJun Shi :
>
> Maybe I didn't describe it clearly. When I use Jenkins, I find that the
> effect
If your looking for how it works
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/PluginManager/index.jelly
https://github.com/jenkinsci/jenkins/blob/c8efc7c78e26f3aefad24ef4c8a161cb9a269ea3/core/src/main/resources/hudson/PluginManager/_table.js#L1-L9
Looks like
If you change your IntelliJ config to delegate to Maven rather than
using its own build code, most of these Maven-specific extensions work
fine (I've had to do that with Maven projects that rely heavily on
Maven toolchain support for example).
On Thu, Nov 28, 2019 at 5:04 PM Joseph P wrote:
>
>
You're likely looking for this plugin:
https://plugins.jenkins.io/throttle-concurrents
The jenkins user mailing list would be likely to get more detailed answers.
On Thu, Nov 28, 2019 at 12:48 AM selva vignesh
wrote:
>
> Hi Team,
> I have written plugin that actually make a apicall to my
Brilliant, thanks :0)
On Mon, Dec 2, 2019 at 7:39 AM Ullrich Hafner
wrote:
> I added you as committer to the repositories.
>
> Am 02.12.2019 um 00:04 schrieb Tony Noble :
>
> Late follow-up, apologies.
>
> Now I have time to look at outstanding PRs / Jira tickets, I still don't
> appear to
Hi everyone,
2.204.1 is scheduled for Dec 18, .2 would be released on Jan 15, with the RC
scheduled for on Jan 1.
I don't expect a lot of backport candidates, or feedback on .1 in general, to
come in between Dec 18 and Jan 1.
Hence I propose we take a two week break as in past years,
We are using Cloudbees plugin to extend Jenkins Credentials and include our
own entry point. We renamed the package and now on a plugin upgrade the
earlier credentials are not retained. Tried below:
//Retain backward compatibility
@Initializer(before = InitMilestone.PLUGINS_STARTED)
I like the postponement idea. +1 from me
On Mon, Dec 2, 2019 at 10:55 AM Daniel Beck wrote:
> Hi everyone,
>
> 2.204.1 is scheduled for Dec 18, .2 would be released on Jan 15, with the
> RC scheduled for on Jan 1.
>
> I don't expect a lot of backport candidates, or feedback on .1 in general,
>
10 matches
Mail list logo
