source-to-image | building artifacts from source and injecting into container | Continuous Deployment library

by openshift Go Version: v1.3.6 License: Apache-2.0

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

kandi X-RAY | source-to-image Summary

source-to-image is a Go library typically used in Devops, Continuous Deployment, Docker applications. source-to-image has no bugs, it has a Permissive License and it has medium support. However source-to-image has 1 vulnerabilities. You can download it from GitHub.

Source-to-Image (S2I) is a toolkit and workflow for building reproducible container images from source code. S2I produces ready-to-run images by injecting source code into a container image and letting the container prepare that source code for execution. By creating self-assembling builder images, you can version and control your build environments exactly like you use container images to version your runtime environments. For a deep dive on S2I you can view this presentation.

Support

Quality

Security

License

Reuse

Support

source-to-image has a medium active ecosystem.

It has 2335 star(s) with 703 fork(s). There are 203 watchers for this library.

It had no major release in the last 12 months.

There are 6 open issues and 369 have been closed. On average issues are closed in 238 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of source-to-image is v1.3.6

Quality

source-to-image has 0 bugs and 0 code smells.

Security

source-to-image has 1 vulnerability issues reported (0 critical, 0 high, 1 medium, 0 low).

source-to-image code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

source-to-image is licensed under the Apache-2.0 License. This license is Permissive.

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

Reuse

source-to-image releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of source-to-image

Get all kandi verified functions for this library.

source-to-image Key Features

No Key Features are available at this moment for source-to-image.

source-to-image Examples and Code Snippets

No Code Snippets are available at this moment for source-to-image.

Community Discussions

Trending Discussions on source-to-image

what is the difference between openshift buildconfig and pipeline

Build image with s2i for local repository

Openshift 3.11 source-to-image (s2i) build using no standard ssh port

QUESTION

what is the difference between openshift buildconfig and pipeline

Asked 2021-Feb-04 at 19:27

I am new to devops and reading openshift docs about this. Seems both buildconfig and pipeline(tekton in openshift 4.6) can achieve source-to-image process and triggered by git webhooks. So what is the difference between openshift buildconfig and pipeline?

PS: Just finished the pipeline tutorial on openshift, there is no build or buildconfig resource created during the whole process.

...

ANSWER

Answered 2021-Feb-04 at 19:27

Openshift buildconfig is "Openshift specific" and was very hot in Openshift3. The hot stuff then was the source2image thing.

Buildconfig could be setup for S2I, Docker and even "Pipeline". But this is not to mix with Openshift Pipelines with Tekton. The BuildConfig pipeliens was provided using jenkins files.

Now as Tekton has gain more stability, respect and maturity out in the community and also under the "Openshift Pipeline" it has been the right way to do stuff.

It is a more complete way to setup complex pipeliens with k8s native way and not only for openshift.

So what the difference more than above I would say that using a pipeline will give you all the flexibility and power as any CI build tool. It is frequently updated and has a great slack community. Buildconfig has lot of limitations on what you can do.

All you can do in buildconfig and more is achievable in Tekton pipeliens, but not the other way around. ;)

When using Openshift Pipelines there are tasks provided for s2i too: https://github.com/openshift/pipelines-catalog

Also Tekton tasks can be added from: https://github.com/tektoncd/catalog

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

QUESTION

Build image with s2i for local repository

Asked 2020-Oct-09 at 12:10

I am trying to build an image using s2i local source code repository following this documentation https://github.com/openshift/source-to-image/blob/master/docs/cli.md . So far I managed to create the image and to generate the s2i scripts using - s2i create test-image s2i_scripts. After that I tried to build the image locally using - s2i build . test-image test-image-app I am running this command while I am in the repository directory.

The result I get after trying to build:

...

ANSWER

Answered 2020-Oct-09 at 12:10

The reason why it was failing was that I didn't pull a base image to use it for my source code. So I pulled centos7 base image - podman pull centos/python-36-centos7 and then I tried to build again and it worked - s2i build . centos/python-36-centos7 test-image-app

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

QUESTION

Openshift 3.11 source-to-image (s2i) build using no standard ssh port

Asked 2020-Jan-17 at 01:30

I'm trying to use OpenShift s2i builds to build an image, pulling source code from a git repo on a non standard port (port 222).

I thought this would be as simple as specifying the port in the git repo url, however this doesnt seem to work. When I run this, I get the following:

...

ANSWER

Answered 2020-Jan-17 at 01:30

To use a port in an ssh URL in Git, use ssh://user@host:port/path/to/repo.git syntax. The shorthand user@host:path syntax does not allow port insertion. The URL you used is the equivalent of:

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

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

Vulnerabilities

No vulnerabilities reported

Install source-to-image

The s2i build workflow is:. Filtering the contents of the source tree is possible if the user supplies a .s2iignore file in the root directory of the source repository, where .s2iignore contains regular expressions that capture the set of files and directories you want filtered from the image s2i produces.
s2i creates a container based on the build image and passes it a tar file that contains: The application source in src, excluding any files selected by .s2iignore The build artifacts in artifacts (if applicable - see incremental builds)
s2i sets the environment variables from .s2i/environment (optional)
s2i starts the container and runs its assemble script
s2i waits for the container to finish
s2i commits the container, setting the CMD for the output image to be the run script and tagging the image with the name provided.
Specify one rule per line, with each line terminating in \n.
Filepaths are appended to the absolute path of the root of the source tree (either the local directory supplied, or the target destination of the clone of the remote source repository s2i creates).
Wildcards and globbing (file name expansion) leverage Go's filepath.Match and filepath.Glob functions.
Search is not recursive. Subdirectory paths must be specified (though wildcards and regular expressions can be used in the subdirectory specifications).
If the first character is the # character, the line is treated as a comment.
If the first character is the !, the rule is an exception rule, and can undo candidates selected for filtering by prior rules (but only prior rules).
You can install the s2i binary using go get which will download the source-to-image code into your $GOPATH, build the s2i binary, and install it into your $GOPATH/bin.
You can start using s2i right away (see releases) with the following test sources and publicly available images:.
Descriptions and examples of the S2I commands
Instructions for using builder images
Guidance for S2I builder image creators
Using a non-builder image for the base of the application image
Troubleshooting and debugging S2I problems

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: