summaryrefslogtreecommitdiffstats
path: root/roles/distgit/files
Commit message (Collapse)AuthorAgeFilesLines
...
* Add a docstring to send_errorMathieu Bridon2015-06-041-0/+9
|
* distgit: Improve error reporting to the clientMathieu Bridon2015-06-041-14/+21
| | | | | | | | | | | | | | | | | There is a send_error method, which sends the error message back to the client. (pyrpkg in our case) Unfortunately, that method doesn't send back an error HTTP status code, which I'm assuming must be interpreted as a "200 OK" status. pyrpkg completely ignore the text sent back by the server, unless the status code is not 200, which means all those errors are silently ignored. This commit makes sure the send_error method will always return an error status ("500 Internal Server Error" by default), and moves all the error handling code to use that method, specifying their own status code if needed.
* Allow git_script_t to create link on NFSPierre-Yves Chibon2015-06-041-0/+3
|
* distgit: Don't raise, return the error to the clientMathieu Bridon2015-06-041-1/+1
| | | | | Raising only sends the error to the logs, the client thinks everything went fine.
* distgit: Actually hardlink over the existing source at the old pathMathieu Bridon2015-05-291-1/+13
| | | | | | | Without this, the file could exist at both the old and new path, taking the space on the disk twice. This forces a hardlink if the file already existed at the old path.
* distgit: And so does os.makedirsMathieu Bridon2015-05-291-1/+1
|
* distgit: os.link fails if the dest already existsMathieu Bridon2015-05-291-1/+7
|
* distgit: Ensure the folder existsMathieu Bridon2015-05-291-2/+3
| | | | | | | We can't hard link the file if the folder containing the link destination does not exist. Hurray for testing in staging!
* distgit: Upload files to both the new and old pathMathieu Bridon2015-05-291-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, the CGI script is set to upload files: - to the old path if the upload uses md5 - to the new path if the upload uses sha512 The old path is as follows: /%(srpmname)s/%(filename)s/%(hash)s/%(filename)s The new path is: /%(srpmname)s/%(filename)s/%(hashtype)s/%(hash)s/%(filename)s This was meant to ensure compatibility with current fedpkg which always downloads from the old path, but will eventually download from the new path when we move to sha512. However, working more on this, I now think it would make for a smoother transition if we instead always stored the files at the new path, but just hardlinked to the old path if the upload is using md5. This is what this patch achieves. With this deployed in production, fedpkg could be patched to try downloading from the new path, and fallback to the old one if necessary, which decouples the migration to the new path from the migration to the new hash.
* Undo this stg/prod distinction.Ralph Bean2015-04-242-74/+3
|
* Try adding a custom cgit header for staging.Ralph Bean2015-04-241-0/+3
|
* Make cgitrc into separate files for prod and staging.Ralph Bean2015-04-241-0/+71
|
* Fix http{s} git cloning on pkgs. Fixes ticket 4688Kevin Fenzi2015-04-231-0/+7
|
* Remove the lookaside email hook (rely on fedmsg now).Ralph Bean2015-03-241-40/+0
|
* Update policies to be compatible with RHEL7Patrick Uiterwijk2015-03-122-6/+8
|
* Fix setup_git_package to handle setting up after gitolite setup a broken repoPatrick Uiterwijk2015-02-271-2/+8
| | | | | | | | | | | | | setup_git_package did the same check as pkgdb_sync did [1]. Also, if gitolite already came by, it will have created an update hook, which blocks us from pushing the initial commit (since gitolite has no idea who we are). So in that case, we will just remove the update hook: gitolite will recreate it when it comes by the repo with genacls.sh. The change to mkdir -p is just synto make it not print an error in case the directory already existed. [1]: https://lists.fedoraproject.org/pipermail/infrastructure/2015-February/015600.html Signed-off-by: Patrick Uiterwijk <puiterwijk@redhat.com>
* Just always take the first commit returned on the master branchPatrick Uiterwijk2015-02-251-1/+1
| | | | | | | Some repos have multiple first master commits due to force-pushes. Without this, that would crash upon branching for those packages. Signed-off-by: Patrick Uiterwijk <puiterwijk@redhat.com>
* Creating branches is now started by genacls.sh.Patrick Uiterwijk2015-02-241-1/+0
| | | | Signed-off-by: Patrick Uiterwijk <puiterwijk@redhat.com>
* Lets first create all repos before creating ACLs for themPatrick Uiterwijk2015-02-231-1/+2
| | | | Signed-off-by: Patrick Uiterwijk <puiterwijk@redhat.com>
* Feel free to run this as root, mmkey?Patrick Uiterwijk2015-02-232-14/+0
|
* Make genacls call pkgdb_sync_git_branches.pyPatrick Uiterwijk2015-02-231-0/+1
| | | | | | | | | | | | gitolite compile creates empty git repos during compile for repos in its acl that don't exist. Since this is automagically run by fedmsg, it triggers before scm-admins can run pkgdb_sync_git_branches.py Because of this, pkgdb_sync_git_branches sees a git repo, thus does not execute setup_git_package. But since setup_git_package creates master, and pkgdb_sync_git_branches later on tries to create new branches from master.... Aka, this broke process-git-requests. Signed-off-by: Patrick Uiterwijk <puiterwijk@redhat.com>
* When a bare repo is created, HEAD is invalid, so cloning won't work.Patrick Uiterwijk2015-02-191-1/+2
|
* Strip unwanted prefix from git.lookaside.new messages.Ralph Bean2015-02-191-0/+4
|
* Try to fix lookaside.new fedmsg messages.Ralph Bean2015-02-191-1/+1
|
* distgit: Add the path to the source file to the emitted messagesMathieu Bridon2015-02-091-1/+4
| | | | | | | | This is the counterpart of this change: https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/170 Now that is has been deployed, we can start emitting the new messages.
* RemiFedora said 0002 was better, especially if we want to access directoriesPierre-Yves Chibon2015-01-301-1/+1
|
* Give other the right to read the filePierre-Yves Chibon2015-01-301-1/+1
| | | | | | This will make cgit happy Thanks Mathieu :)
* Add our own SELinux policy for upload.cgiPierre-Yves Chibon2015-01-282-0/+25
| | | | Many thanks to tfirg on #selinux for helping out making this policy
* distgit: Don't try reloading apache if it's offMathieu Bridon2015-01-271-1/+1
|
* Revert "distgit: Merge in the cgit/make_pkgs_list role"Mathieu Bridon2015-01-271-14/+0
| | | | | | | | | This reverts commit a29f50a19a3839c12e609a22f8cd319e553da7a0. Turns out, Fedora People needs this as well, so it needs to remain separated. Sorry for the noise!
* distgit: Merge in the cgit/make_pkgs_list roleMathieu Bridon2015-01-271-0/+14
| | | | | | | | Having it split out was causing trouble, because distgit depends on it, but it depends on the /srv/git folder being created, which is created in the distgit role... Nothing else uses this though, so merging it is the easy way out.
* lookaside: Try again allowing the CGI scriptMathieu Bridon2015-01-261-2/+3
|
* lookaside: Also grant access for the uploadMathieu Bridon2015-01-261-0/+2
|
* In EL7 we need to specify who can accessPierre-Yves Chibon2015-01-261-0/+1
|
* Drop ; thats causing an error. Need to merge this with koji hub version.Kevin Fenzi2015-01-231-1/+1
|
* Restorecon and restart apache after installing the new certPierre-Yves Chibon2015-01-231-0/+2
|
* When updating the crl, take into account that there might not be one alreadyPierre-Yves Chibon2015-01-231-7/+11
|
* distgit: Remove the update-chained stuffMathieu Bridon2015-01-231-10/+0
| | | | This doesn't work with Gitolite.
* Set the local_code folder in full pathPierre-Yves Chibon2015-01-231-1/+1
|
* Add the gitolite update hookPierre-Yves Chibon2015-01-231-0/+4
|
* Run the compile as root but then specify the HOME variablePierre-Yves Chibon2015-01-231-1/+1
|
* Indicate where we list the pkgs adminsPierre-Yves Chibon2015-01-221-0/+1
|
* No need to install our hook ourself anymorePierre-Yves Chibon2015-01-221-6/+6
|
* Activate the site-local gitolite codePierre-Yves Chibon2015-01-221-1/+1
|
* Fix path to the gitolite update hookPierre-Yves Chibon2015-01-211-1/+1
|
* Let the gen-acls user compile the configuration filePierre-Yves Chibon2015-01-201-1/+2
|
* Drop the -s/--source branch argument in mkbranchPierre-Yves Chibon2015-01-131-17/+3
| | | | | | | | | | | | In the process of automating the git branch creation based on fedmsg message we can no longer rely on passing a -s/--source branch argument to the mkbranch script. As decided in https://fedorahosted.org/rel-eng/ticket/5931 the branches will be created with the first commit of the master branch. This commit thus drops the use of -s/--source and SRC_BRANCH in favor of creating the branch with the first commit of the master branch: git branch --no-track $BRANCH `git rev-list --max-parents=0 master`
* Replace tab with spacesPierre-Yves Chibon2015-01-131-47/+47
|
* Remove process-git-requests from distgit roleTill Maas2015-01-121-654/+0
| | | | The script is maintained in rel-eng repo. The version here is outdated.
* Do not install nor configure the email-libravatar script while the package ↵Pierre-Yves Chibon2014-12-161-1/+1
| | | | isn't in epel7
generated by cgit (git 2.34.1) at 2025-10-02 17:30:21 +0000