Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
I
inau
Manage
Activity
Members
Labels
Plan
Issues
5
Issue boards
Milestones
Wiki
Code
Merge requests
2
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
cs
util
inau
Commits
01097616
Commit
01097616
authored
2 years ago
by
Alessio Igor Bogani
Browse files
Options
Downloads
Patches
Plain Diff
Add a possible workaround for exit status 128 as comment
parent
9831f553
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
inau-dispatcher.py
+4
-0
4 additions, 0 deletions
inau-dispatcher.py
with
4 additions
and
0 deletions
inau-dispatcher.py
+
4
−
0
View file @
01097616
...
...
@@ -15,6 +15,7 @@ import logging
import
logging.handlers
import
argparse
import
datetime
#import time
import
subprocess
import
paramiko
import
hashlib
...
...
@@ -94,6 +95,9 @@ class Builder:
def
update
(
self
,
job
):
logger
.
info
(
"
[
"
+
self
.
name
+
"
] Checkouting
"
+
job
.
build_tag
+
"
from
"
+
job
.
repository_url
+
"
...
"
)
builddir
=
self
.
platdir
+
"
/
"
+
job
.
repository_name
# Wait a second before start to update git repository to avoid:
# Command '['git -C /scratch/build/repositories//8/cs/etc/browser/booster reset --hard refs/tags/1.0.34']' returned non-zero exit status 128.
# time.sleep(1)
if
not
os
.
path
.
isdir
(
self
.
platdir
):
os
.
mkdir
(
self
.
platdir
)
if
os
.
path
.
isdir
(
builddir
):
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment