Hello Francisco,
I am off for this week and focusing on Jenkins anyway these days, so you
can go ahead with your attempts.
To test it might be easier to first implement using "core" actions and only
then after you validate it's working in the organization to move it to
kogito-pipelines - so that way you can make PRs only against
kogito-runtimes let's say.

Regards
Jan

Dne út 26. 9. 2023 9:54 uživatel Francisco Javier Tirado Sarti <
[email protected]> napsal:

> Just to coordinate, are you working to fix it (I guess through
> replacing that action) or should I give it a try (I'm not pretty confident
> I can fix since my level of knowledge regarding GHA is lower than my Cobol,
> but you never know)?
>
> El lun, 25 sept 2023 a las 19:44, Jan Šťastný (<[email protected]>)
> escribió:
>
> > Yes it's the 'maven' action of incubator-kie-kogito-pipelines/.ci/actions
> >
> > Dne po 25. 9. 2023 18:23 uživatel Francisco Javier Tirado Sarti <
> > [email protected]> napsal:
> >
> > > Ok, now the error is the same in both PRs
> > > Error: Bad request - whelk-io/maven-settings-xml-action@v21 is not
> > allowed
> > > to be used in apache/incubator-kie-kogito-runtimes. Actions in this
> > > workflow must be: within a repository owned by apache, created by
> GitHub,
> > > verified in the GitHub Marketplace, or matching the following:
> > > */*@[a-f0-9][a-f0-9][a-f0-9][a-f0-9][a-f0-9][a-f0-9][a-f0-9]+,
> > > AdoptOpenJDK/install-jdk@*,
> > >
> > >
> >
> JamesIves/github-pages-deploy-action@5dc1d5a192aeb5ab5b7d5a77b7d36aea4a7f5c92
> > > ,
> > > TobKed/label-when-approved-action@*, actions-cool/issues-helper@*,
> > > actions-rs/*, al-cheb/configure-pagefile-action@*,
> > > amannn/action-semantic-pull-request@*, apache/*,
> > > burrunan/gradle-cache-action@*,
> > > bytedeco/javacpp-presets/.github/actions/*,
> > > chromaui/action@*, codecov/codecov-action@*,
> > > conda-incubator/setup-miniconda@*, container-tools/kind-action@*,
> > > container-tools/microshift-action@*, dawidd6/action-download-artifact@
> *,
> > > delaguardo/setup-graalvm@*, docker://jekyll/jekyll:*,
> > > docker://pandoc/core:2.9, eps1lon/actions-label-merge-conflict@*,
> > > gaurav-nelson/github-...
> > >
> > > I guess whelk-io/maven-settings-xml-action is invoked in some of the
> > > kogito-pipelines actions.
> > >
> > >
> > > El lun, 25 sept 2023 a las 18:13, Francisco Javier Tirado Sarti (<
> > > [email protected]>) escribió:
> > >
> > > > They are even changed already in the runtimes yaml,  see
> > > >
> > >
> >
> https://github.com/apache/incubator-kie-kogito-runtimes/commit/205adb018a010632dadef0050805305542a1e73a#diff-0371439771cb78638f1c5b9e364dcd090a9626bfc0b05980359c8e5c83fe40eeR45
> > > > Somehow, that PR did not pick up them.
> > > >
> > > > El lun, 25 sept 2023 a las 18:08, Davide Salerno (<
> > > > [email protected]>) escribió:
> > > >
> > > >> yes it seems that all the actions required for kogito-runtimes are
> > > already
> > > >> "cherry-picked" in that repo so we could simply use the
> > > >> (incubator-kie-)kogito-pipelines in all the projects we need those
> > > >> actions.
> > > >>
> > > >> Il giorno lun 25 set 2023 alle ore 17:59 Roberto Oliveira <
> > > >> [email protected]> ha scritto:
> > > >>
> > > >> > It seems those actions also exist on the kogito-pipelines
> repository
> > > >> > in Apache? I mean here
> > > >> >
> > > >> >
> > > >>
> > >
> >
> https://github.com/apache/incubator-kie-kogito-pipelines/tree/main/.ci/actions
> > > >> > ,
> > > >> > maybe you can migrate to use them instead of kie-ci?
> > > >> >
> > > >> > On Mon, 25 Sept 2023 at 12:44, Francisco Javier Tirado Sarti
> > > >> > <[email protected]> wrote:
> > > >> > >
> > > >> > > The problem is that the github action for kogito-runtimes repo
> is
> > > not
> > > >> > > working because, apparently (as I interpret the message, I'm not
> > > >> familiar
> > > >> > > with the action, but an user of it ;)), is making
> > > >> > > use of these other actions located at that repository.
> > > >> > > So wondering which is the best plan to make this work?
> > > >> > >
> > > >> > > El lun, 25 sept 2023 a las 17:39, Roberto Oliveira (<
> > > >> > > [email protected]>) escribió:
> > > >> > >
> > > >> > > > Do we plan to migrate kie-ci to Apache? AFAIK this repository
> is
> > > >> more
> > > >> > > > related to the product itself and not much with community.
> > > >> > > >
> > > >> > > > On Mon, 25 Sept 2023 at 12:33, Francisco Javier Tirado Sarti
> > > >> > > > <[email protected]> wrote:
> > > >> > > > >
> > > >> > > > > Regarding issues with github for kogito-runtimes
> > > >> > > > >
> > > >> > > > >
> > > >> > > >
> > > >> >
> > > >>
> > >
> >
> https://github.com/apache/incubator-kie-kogito-runtimes/actions/runs/6199943114
> > > >> > > > >
> > > >> > > > > kiegroup/kie-ci/.ci/actions/ubuntu-disk-space@main,
> > > >> > > > > kiegroup/kie-ci/.ci/actions/long-paths@main,
> > > >> > > > > kiegroup/kie-ci/.ci/actions/maven@main,
> > > >> > > > > kiegroup/kie-ci/.ci/actions/build-chain@main, and
> > > >> > > > >
> kiegroup/kogito-pipelines/.ci/actions/action-junit-report@main
> > > >> are
> > > >> > not
> > > >> > > > > allowed to be used in apache/incubator-kie-kogito-runtimes.
> > > >> Actions
> > > >> > in
> > > >> > > > this
> > > >> > > > > workflow must be: within a repository owned by apach
> > > >> > > > >
> > > >> > > > > If I understand correctly, we should be migrating kie-ci to
> > > >> Apache,
> > > >> > isnt
> > > >> > > > it?
> > > >> > > >
> > > >> > > >
> > > >>
> ---------------------------------------------------------------------
> > > >> > > > To unsubscribe, e-mail: [email protected]
> > > >> > > > For additional commands, e-mail: [email protected]
> > > >> > > >
> > > >> > > >
> > > >> >
> > > >> >
> > ---------------------------------------------------------------------
> > > >> > To unsubscribe, e-mail: [email protected]
> > > >> > For additional commands, e-mail: [email protected]
> > > >> >
> > > >> >
> > > >>
> > > >> --
> > > >> Davide Salerno
> > > >>
> > > >> E: [email protected]
> > > >> S: davide.salerno
> > > >> M: +39 347 80 44 258
> > > >> W: http://www.davidesalerno.net
> > > >>
> > > >
> > >
> >
>

Reply via email to