#9334 Create place for ELN compose configuration files.
Closed: Fixed 4 years ago by mohanboddu. Opened 4 years ago by jkaluza.

Hi,

the ELN project (https://fedoraproject.org/wiki/ELN) will be building composes using ODCS. We therefore need a place where the compose configuration of these composes can be stored. I've discussed that with @mohanboddu and we both agreed official git repositories with composes will be the best place to store them.

I'm therefore asking Fedora releng to implement following changes:

  • Add eln branch to https://pagure.io/pungi-fedora/ and grant jkaluza permissions to merge the PRs related to this branch. I know we cannot setup it in a way that jkaluza has these rights only for eln, but the deal is I will be merging just PRs done against the eln branch and will not touch other branches.
  • Add eln branch to https://pagure.io/releng/fedora-module-defaults/ and grant jkaluza permissions to merge the PRs related to this branch. The same applies as for the previous point.
  • Grant jkaluza permissions to merge PRs in the https://pagure.io/fedora-comps/tree/master. I will create new comps-eln.xml.in file there and I will maintain it. I will not touch other files.

Once the change request is approved, we can do the needful.

@mohanboddu, th ELN change request has been approved (https://pagure.io/fesco/issue/2365). I thiink we can proceed with this ticket now and created the branches and grant permissions, right? :)

Add eln branch to https://pagure.io/pungi-fedora/ and grant jkaluza permissions to merge the PRs related to this branch. I know we cannot setup it in a way that jkaluza has these rights only for eln, but the deal is I will be merging just PRs done against the eln branch and will not touch other branches.
Add eln branch to https://pagure.io/releng/fedora-module-defaults/ and grant jkaluza permissions to merge the PRs related to this branch. The same applies as for the previous point.
Grant jkaluza permissions to merge PRs in the https://pagure.io/fedora-comps/tree/master. I will create new comps-eln.xml.in file there and I will maintain it. I will not touch other files.

Given commit access to the repo, you can create the eln branches from the scratch or one of the existing branches and same with creating the eln comps file.

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 years ago

@mohanboddu, not sure if I'm doing it right, but I've tried to create new "eln" branch by simply creating it in my local pungi-fedora copy and pushing it. This failed with:

$ git push --set-upstream origin eln
Enumerating objects: 7, done.
Counting objects: 100% (7/7), done.
Delta compression using up to 4 threads
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 2.42 KiB | 2.42 MiB/s, done.
Total 5 (delta 0), reused 0 (delta 0)
remote: Has commit access: True
remote: Commit 030372576bb9646e76b7a61ebf220be87cd2d23e is not signed
remote: Commit 030372576bb9646e76b7a61ebf220be87cd2d23e is not signed
To ssh://pagure.io/pungi-fedora.git
 ! [remote rejected] eln -> eln (pre-receive hook declined)
error: failed to push some refs to 'ssh://git@pagure.io/pungi-fedora.git'

Login to comment on this ticket.

Metadata