Pipelines Without Buildpacks
This lesson demonstrates how to create a pipeline without a build pack.
We'll cover the following
While the idea behind build packs is to cover a wide range of use cases, we might be in a situation when what we want to accomplish is fundamentally different from any of the build packs. In such cases, it doesn’t make sense to have a pipeline based on a build pack. Instead, we can tell Jenkins X that our pipeline is not based on any build pack.
Creating a pipeline without a buildpack#
Please execute the command that follows to create a pipeline without a buildpack.
In this context, the only line that matters is the first one that instructs Jenkins X not to use any buildPack by setting the value to none. The rest of the pipeline contains an example of constructs that we already explored.
Confirming the changes#
Now, let’s push the change and confirm that none of the build packs is used by observing the activities.
The output of the last command, limited to the newest activity, is as follows.
We can see that all the steps we normally get from a build pack are gone. We are left only with the generic Git-related steps and the silly one we defined in our pipeline.
Please stop watching the activities by pressing ctrl+c.
In the next lesson, we will see how to check the full syntax schema of constructs.
