Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] Fwd: [GitHub Support] - Jobs stuck in queue for hours 
Mickael Istria schrieb am 29.03.2023 um 14:57:
> The eclipse-dev mailing-list is the mailing-list of Eclipse project
> (that is Equinox + Platorm + JDT + PDE) developers.

Sorry, I thought that it was a mailing list across all Eclipse projects.
I really wanted to address other projects too, not just Eclipse IDE
developers, in order to trigger everyone to consider moving their
projects into their own organisations in order to escape from the same
trap AspectJ is in at the moment, having our repositories in the
"eclipse" organisation on GitHub. Do you happen to know if there is a
way to address all projects? Maybe the infra people could to that.


> The GitHub repositories for the Eclipse project are part of a dedicated
> organization already for various reasons

I am aware of that. The mistake was to falsely deduce from the mailing
list name that the list might be more general than is actually true, see
above.

> I suspect you should redirect your discussion to the AspectJ/AJDT
> project mailing-list

No, that is the opposite of what I want. Moreover, I would be talking to
myself there.

> or Eclipse infra team.

Yes, thast might be more promising.


Jonah Graham schrieb am 29.03.2023 um 15:37:

> I recommend you request helpdesk move AspectJ to its own org like I
> did here for LSP4J
>
> https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/2805

We have had such an issue for 6+ months already:
https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/1742

It is currently blocked by the fact that we want to merge the AspectJ
and AJDT projects into one, moving both into the same GH organisation.
Someone needs to approve that, i.e. there is paper work which the
project lead did not have enough time for so far. But we are getting
there. It is just not helping me today.

In order to compensate people here on this list for annoying them with
my issue, here is a little tidbit for you, should ever be affected by a
situation of too many builds going on at the same time in your GH
organisation: Simply fork the project, push to your private fork and
trigger the build workflow there manually for the branch you want. I
always make sure that my GH workflows contain the option of triggering
them manually, using the "workflow_dispatch" build option:

name: Build AspectJ

on:
  push:
    branches: [ master ]
  pull_request:
    branches: [ master ]
  workflow_dispatch:

jobs:
  ...

Back to the top