Seems to be happening again now
https://p.datadoghq.com/sb/0Igb9a-dca9738dbb5048025c005182a8f240c0
On Wed, 2 Oct 2019 at 15:14, Paul Allen wrote:
> Thanks - It seems to be working now.
>
> > On 2 Oct 2019, at 10:24, Olblak wrote:
> >
> > As you can see on this status page, there is definitely
I wanted to also add that I do not feel using github actions will bring us any
value.
{
"regards" : {
"name" : “marky”,
"phone" : "+1 (408) 464 2965”,
"email" : “marky.r.jack...@gmail.com",
"team" : “jackson5“,
“role” : “software engineer"
> On 3. Oct 2019, at 08:58, Maria Narcisa Gălan
> wrote:
>
> I am not sure what to do in this situation, any suggestions?
https://jenkins.io/doc/developer/publishing/removing-from-distribution/ is our
documentation for this.
--
You received this message because you are subscribed to the
While I understand the value of Github Actions, I would not enable it on
jenkins-infra unless we have a good reason to do so.
I understand that ci.jenkins.io has limitations for various reasons and if we
have them other people will face the same issues.
But using ci.jenkins.io is really useful
Hi,
It is possible to blacklist the invalid release in the update center.
Example: https://github.com/jenkins-infra/update-center2/pull/293/files
Hopefully it helps,
On Thursday, October 3, 2019 at 11:33:43 AM UTC+2, Maria Narcisa Gălan
wrote:
>
> Hey,
>
>
> I made a plugin release with a
In my experience, you can still release 5.9.1. But the least version should
also be 6.0.1. Unless someone helps you to delete 6.0.1 from the nexus.
Or you can put it into a blacklist
https://github.com/jenkins-infra/update-center2/blob/master/src/main/resources/artifact-ignores.properties
.
On
Hey,
I made a plugin release with a wrong version.
The next version should have been 5.9.1 and not 6.0.1 since 6.0 is not
released yet.
I am not sure what to do in this situation, any suggestions?
Thanks!
--
You received this message because you are subscribed to the Google Groups
I can be the default assigner. At least people can get a response as soon
as possible.
On Thu, Oct 3, 2019 at 4:49 PM Oleg Nenashev wrote:
> Hi,
>
> Sorry for forgetting about this action item.
> Permission transfer is done. Please let me know if you want to become a
> default assignee (it is
Hi,
Sorry for forgetting about this action item.
Permission transfer is done. Please let me know if you want to become a
default assignee (it is removed now).
Best regards,
Oleg Nenashev
On Thursday, September 26, 2019 at 8:28:57 AM UTC+2, Rick wrote:
>
> Hi team,
>
> Thanks for the response
GitHub Actions is pretty useful for organization automation, e.g. when you
want to run Dependabot, Release Drafter or other bot with some custom
configurations.
I do not see how ci.jenkins.io could be used as a replacement for it taking
the permission considerations. And I doubt it worth
10 matches
Mail list logo
