I could see some bash commands in the CI/CD section of the tool. But is there any case study or proven case where the cases would be integrated with AWS Codebuild please ? Also is it Supported with testRigor at the moment ? If Yes, can you explain how ?
Yes, AWS CodeBuild is supported by testRigor out of the box.
The way it works is you copy the script from CI/CD section and paste it as a bash script which is triggered in CodeBuild. Works out of the box.
I know it is not exactly the same but here is a video showing how to use it with GitHub Actions which is hopefully will clarify some things: https://youtu.be/f8QFFHBywto
Related
I have one DevOps project which has a build pipeline and a release pipeline. creation of build pipeline, DevOps project, container registry, service connection, and Kubernetes cluster is automated using terraform, ARM templates and AZCLI. I could not find any way to store the release pipeline as a code. Is there any way to do that? I want to know how other people are dealing with this? Is there something I am missing?
I could not find any way to store the release pipeline as a code. Is
there any way to do that? I want to know how other people are dealing
with this? Is there something I am missing?
Looks like you're looking for multi-stage Yaml pipelines like Daniel commented above. For now, we can't directly create release pipeline as Yaml format, but we can use multi-stage Yaml for both CI and CD.
To use that option, we need to enable the Multi-stage
pipelines in Preview Features.
You may get more useful info from this issue and this blog. Hope it helps.
Does AWS CodeBuild already has aws-cli installed? If yes, do i still need to configure a profile or a role attached to codebuild would be sufficient?
Best Regards
For the first question, the answer is 'Yes'. The curated images have the aws-cli installed.
For the second question, the service role you provided in the project would be use, but you could still configure your profile if you want to.
Just to make it clearer and concise: CodeBuild can't have aws-cli installed, but the images it uses to run a build can have it.
Images managed by AWS CodeBuild do have AWS CLI and you can verify it by simply adding aws --version to one of you commands (pre_build might be a good place for that).
Same check can be done for the custom images, if you're not sure.
You can find more details on the Github page on what packages are installed in the images. In the AWS documentation you can find the links to the according Github pages.
I'd like to use Travis to push a static HTML/JavaScript website to an Amazon S3 bucket on each commit to master. Is there any way to configure my .travis.yml so it doesn't try to run any sort of build process? Just a deploy?
It seems like this is mainly controlled by the language setting which defaults to Ruby, so Ruby is being (unnecessarily) installed on each build.
I don't know how the ruby box works (I use the java box for my work); that being said, I think that the travis CI boxes have their base language already installed so you aren't really unnecessarily installing ruby each time.
If you want, there supposedly is an undocumented option language: generic.
This way you can just run the required bash commands to deploy your code to Amazon S3
Are there any plugins available for this? Does SoapUI offer plugins/addins anyway?
Thank.
It is not clear what you are asking.
SoapUI generates a soapui.log by default in the current working directory. Basic information is available in the official documentation, under the heading "Tip 7) Read the Log".
As for plugins: yes there are plugins available, and described in the official documentation as well.
Update:
If you are after logs of all the calls you made, then you need to launch the test runner with the -a or -A switch. As always official documentation is available for launching from the GUI or CLI.
Don't actually know if SOAPUI has any kind of plugins. But you could create your own reporting structure, which would be really cool because you can customize it however you want to. In our project, we write the expected and update the actual values into the data sink and write the test status into the same, all using the groovy script :)
I'm trying to create a Jenkins job to spin up a VM on Amazon EC2 based on an AMI that I currently have saved. I've done my searching and can't find an easy way to do this other than through Amazon's GUI. This isn't very ideal as there are a lot of manual steps involved and it's time-consuming.
If anyone's had any luck doing this or could point me in the right direction that would be great.
Cheers,
Darwin
Unless I'm misunderstanding the question this should be possible using the cli, assuming you can install and configure the cli on your jenkins server you can just run the command as a shell script as part of the build.
Create an instance with CLI.
The command would be something along the lines of:
[path to cli]/aws ec2 run-instances --image-id ami-xyz
If your setup is too complicated for a single cli command, I would recommend creating a simple cloudformation template.
If you are unable to install the cli, you could use any number of sdk's e.g. java to make a simple application you could run with jenkins.
There is the Jenkins EC2 Plugin
Looking at the document it looks like you may be able to reuse your AMI. If not, you can configure it with an init script
Next, configure AMIs that you want to launch. For this, you need to
find the AMI IDs for the OS of your choice. ElasticFox is a good tool
for doing that, but there are a number of other ways to do it. Jenkins
can work with any Unix AMIs. If using an Ubuntu EC2 or UEC AMI you
need to fill out the rootCommandPrefix and remoteAdmin fields under
'advanced'. Windows is currently unsupported.