gitlab-art | cross-project Gitlab artifact dependencies | Computer Vision library

by kosma Python Version: 0.4.0 License: WTFPL

X-Ray Key Features Code Snippets(1)Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | gitlab-art Summary

gitlab-art is a Python library typically used in Artificial Intelligence, Computer Vision applications. gitlab-art has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can install using 'pip install gitlab-art' or download it from GitHub, PyPI.

art solves a burning problem of pulling artifacts from different repositories.

Support

Quality

Security

License

Reuse

Support

gitlab-art has a low active ecosystem.

It has 9 star(s) with 3 fork(s). There are 2 watchers for this library.

There were 1 major release(s) in the last 12 months.

There are 5 open issues and 7 have been closed. On average issues are closed in 56 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of gitlab-art is 0.4.0

Quality

gitlab-art has no bugs reported.

Security

gitlab-art has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

gitlab-art is licensed under the WTFPL License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

gitlab-art releases are available to install and integrate.

Deployable package is available in PyPI.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed gitlab-art and discovered the below as its top functions. This is intended to give you an instant insight into gitlab-art implemented functionality, and help decide if they suit your requirements.

Return a list of artifacts in artifacts_lock
Install a member
Create directories
Return a file - like object
Load yaml file
Returns the path to the cache file
Return the name of a zip file
Download artifacts
Save a file
Return a Gitlab instance
Update the artifacts
Returns the latest job that matches the ref
Saves the configuration file
Return the contents of a project file
Configure the application

Get all kandi verified functions for this library.

gitlab-art Key Features

No Key Features are available at this moment for gitlab-art.

gitlab-art Examples and Code Snippets

art - cross-project Gitlab artifact dependencies,Continuous integration

Python

Lines of Code : 8

License : Permissive (WTFPL)

Copy

before_script:
  - sudo pip install https://github.com/kosma/art
  - art configure  
  - art download
  - art install
cache:
  paths:
    - .art-cache/

Community Discussions

Trending Discussions on gitlab-art

“500 Internal Server Error” with job artifacts on minio

Gitlab through traefik with Docker-compose

QUESTION

“500 Internal Server Error” with job artifacts on minio

Asked 2021-Jun-14 at 18:30

I'm running gitlab-ce on-prem with min.io as a local S3 service. CI/CD caching is working, and basic connectivity with the S3-compatible minio is good. (Versions: gitlab-ce:13.9.2-ce.0, gitlab-runner:v13.9.0, and minio/minio:latest currently c253244b6fb0.)

Is there additional configuration to differentiate between job-artifacts and pipeline-artifacts and storing them in on-prem S3-compatible object storage?

In my test repo, the "build" stage builds a sparse R package. When I was using local in-gitlab job artifacts, it succeeds and moves on to the "test" and "deploy" stages, no problems. (And that works with S3-stored cache, though that configuration is solely within gitlab-runner.) Now that I've configured minio as a local S3-compatible object storage for artifacts, though, it fails.

...

ANSWER

Answered 2021-Jun-14 at 18:30

The answer is to bypass the empty-string test; the underlying protocol does not support region-less configuration, nor is there a configuration option to support it.

The trick is able to work because the use of 'endpoint' causes the 'region' to be ignored. With that, setting the region to something and forcing the endpoint allows it to work:

Source https://stackoverflow.com/questions/67005428

QUESTION

Gitlab through traefik with Docker-compose

Asked 2019-Oct-16 at 13:06

I have been trying for several days to run gitlab via docker-composing through Traefik. I found several topics about it but none of them really solved my problem. So I would like to open a topic today.

I have helped myself a lot with the following example: https://github.com/ambroisemaupate/docker-server-env/blob/master/compose/example-gitlab-traefik/docker-compose.yml

...

ANSWER

Answered 2019-Oct-16 at 13:06

This is a syntax error in the next line:

Source https://stackoverflow.com/questions/58394706

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install gitlab-art

Create a Gitlab private token and save it in art configuration:.
Create a Gitlab private token and save it in art configuration: art configure https://gitlab.example.com/ 'as1!df2@gh3#jk4$'
Create artifacts.yml with definitions of needed artifacts: - project: kosma/foobar-documentation ref: branches/stable job: doc install: build/apidoc/html/: docs/api/ VERSION: docs/VERSION - project: kosma/foobar-firmware ref: 1.4.0 job: firmware-8051 install: build/8051/release/firmware.bin: blobs/firmware-8051.blob - project: kosma/foobar-icons ref: 69881ebc852f5e02b8328c6b9da615e90b7184b2 job: icons install: .: icons/
Run art update to automatically determine latest versions and job numbers of needed projects and save them into artifacts.lock.yml. Commit both files to version control system.
Run art download to fetch required artifacts to your local cache and art install to install them to the project directory.

Support

Gitlab's $CI_BUILD_TOKEN infrastructure doesn't support accessing artifacts, so a private token must be used. This is very unfortunate and kludgey. This might be fixed in future Gitlab releases (if I bug them hard enough).Multiple Gitlab instances are not supported (and would be non-trivial to support).Error handling is very rudimentary: any non-trivial exceptions simply propagate until Python dumps a stack trace.Logging could be improved.Format of the artifacts.yml file is not checked and is barely documented.Some breakage may occur with non-trivial use cases.Like with any other build system, security depends on trusting the developer not to do anything stupid. In particular, paths are not sanitized; with enough ingenuity one could probably escape the build directory and wreak havoc.There is no uninstall command. If you changed artifact versions and need to have a clean slate, it's highly recommended to run git clean -dfx (beware, however: any local changes to your working copy will be lost without warning).There are probably cleaner solutions to this problem, like using some sort of cross-language package manager; however, I didn't find any that would satisfy my needs.

Find more information at: