I see 1.1 at http://updates.jenkins-ci.org/download/plugins/zohosprints/
i also see 1.0.2, which you don't seem to have a tag/release for
I'm very confused by the state of your repo.
On Mon, Apr 6, 2020 at 8:41 PM selva vignesh
wrote:
> yes Slide. I am referring releasing plugin as a build.
yes Slide. I am referring releasing plugin as a build. Sorry for the
confusion.
Sure Gavin. I will release one more build without hyphen.
On Tue, Apr 7, 2020 at 9:08 AM 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:
> 11 days ago is a suspicious number, none of
11 days ago is a suspicious number, none of them line up with
https://github.com/jenkinsci/zohosprints-plugin/releases
I'm honestly not sure what will happen when you add values after the
version number (ex 1.0.3-docrelease), i know beta and alpha goto
experimental. Can you do a proper "1.0.3" or
When you say updated a build,do you mean you create a new release of the
plugin? Can you point to your pom.xml?
On Mon, Apr 6, 2020 at 8:34 PM selva vignesh
wrote:
> Hi,
> After adding value to GitHub repo nothing changed. I have updated a
> build yesterday but still in plugin page showing
Hi,
After adding value to GitHub repo nothing changed. I have updated a
build yesterday but still in plugin page showing that Last release was 11
days ago. can anyone please assist
On Thu, Apr 2, 2020 at 3:23 PM Richard Bywater wrote:
> Hi
>
> The value in your pom.xml needs to point at your
Totally love the roadmap. Sincerely missed in most software.
Rgds
Jon
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Ok,
1. I merged your PR and the reviewed one. Locally it builds for me, but
should take a look at where its building in the CI, so I can monitor errors
- is there a url?
2. Imported the README in to the git repo, thanks for the link. WIll try
clear it up once the code is building and breathing.
Hi all,
I'm working on restyling the buttons as part of the UX SIG improvements. My
approach for updating the styles is to reuse the YUI CSS classes. The
reason is to keep backwards compatibility and ensure all buttons are
updated across the ecosystem. Sample markup that stays the same:
yes, we have a standard Pipeline for Plugin in Jenkins. I have submitted a
pull request for CI here:
https://github.com/jenkinsci/configurationslicing-plugin/pull/26. Plugin
POM is pretty old, and update to recent versions is needed for advanced
checks in our Pipeline
.Also, I would recommend to
Hey Oleg, thanks for your help!
Its crazy times for all and perfectly understandable. Glad to do some FOSS
help meanwhile.
Question - assuming that PR passes review I presume now that I should make
sure this repo is also built and published - is there some doc on how to do
that? I built it and
Hi all,
There was no new breaking changes coming in, and I think it is time to go
ahead and release a 4.0 version.
I plan to do so tomorrow if there is no negative feedback.
It would be great if somebody could write a blogpost with a summary of the
changes in the new major release
P.S: 4.0
11 matches
Mail list logo
