https://github.com/git-time-metric/gtm is a set of tools that allow to track time on Git.

The latest release can be installed automatically using brew or manually by installing the executables listed https://github.com/git-time-metric/gtm/releases/tag/v1.3.5 .

gtm must first be initialized (gtm init) from with the git project directory to allow time tracking. When you commit your work, gtm then saves the time associated with your commit.

The time can be displayed using the gtm report command; format argument timeline-hours allows to create a Gantt chart.

On a side note, I am not sure whether gtm can help with existing projects. I tried running it onto one of my repos and it logged 0s for all my previous commits.

One goal of DevOps is to create reproducible, production-like environments from source-code repositories. To achieve this, I believe it's necessary to also restore all the data that is needed to setup the environment, so that automated & manual tests can be run there.

For example, let's take a CMS product that provides content (labels, images, rich-text) to a user-facing web application. We want to run integrations tests or explorative UI tests against that web application using production-like data from the CMS. Due to the nature of the product, the data itself can be manipulated at any time by users using the UI of the CMS.

There are two main use cases

• Developers create example content or add required label translations for new features
• Content managers publish new content for production, which may include static content like label translations

In a typical setup, there are at least two environments, let's say staging and production. Due to the use cases described above, the CMS databases where the contents are stored will deviate quite quickly between these environments.

Without taking any measures here, after a while, the two databases will be completely out-of-sync and the staging database will not be "production-like" anymore. Additionally, each release of a new feature will require manual steps to add data like label translations into the production database, a step that is neither verified nor tested before the release.

So my question is: What is a good way to bring new "baseline" data from a staging database into a production database without overriding the changes there. And was is a good way to bring back data from production into the staging environment, to provide production-like data for testing purposes. Ideally, all automated and all part of version-control.

Side Note: If we say "different CMS content doesn't change anything about testing", let's think of another use-case where the data behaves even more like configuration. For example, payment or delivery options that are offered on an e-Commerce site.

I'm running an azure build pipeline for a dockerized application set up using an azure-pipelines.yml file. The problem is that we require a build arg passed through to the docker build command, but the arg is blank in all circumstances (even if no build arg is provided and a default is specified in the Dockerfile).

Snippet of azure-pipelines.yaml (sensitive data changed only):

- task: Docker@2
  displayName: build
  inputs:
    containerRegistry: our_container_registry
    repository: $(Build.Repository.Name)
    command: build
    Dockerfile: '**/Dockerfile'
    tags: $(Build.BuildNumber)
    arguments: --build-arg BuildNumber=$(Build.BuildNumber)

Further details:

• We are using the VM image of ubuntu-latest to run the job
• The build arg appears to be being passed through correctly as it does appear in the printout of the command that is run
  • e.g. if we pass --build-arg BuildNumber=1.2.3 as part of the arguments property of the yaml file, we'll see --build-arg BuildNumber=1.2.3 on the printout of the command run.
• As can be seen from the above snippet we're not running the buildAndPush command that I am aware has issues with build args (publish is it's own step we're not even getting to yet).
• The Dockerfile contains the command RUN echo Build Number: ${BuildNumber} which prints out Build Number: during the build.
• Running the same build command printed out by the build step locally builds the container with no errors, and prints out the build number appropriately in the above mentioned command

I'm looking for an explanation as to how I can get the build args passed through correctly to our docker build, or if there is something we're not aware of preventing this then recommendations of other alternatives that would achieve the same ends.

you add the server to balancer then create NAT rule to forward the packet to specific port on your VM.

https://argonsys.com/microsoft-cloud/library/manage-port-forwarding-for-backend-pool-with-azure-load-balancer/

When I run any kubectl commands, I'm getting

The connection to the server localhost:8080 was refused - did you specify the right host or port?

We have a ROSA (Openshift on AWS) cluster, working fine with all kinds of domains except one, which happens to be an apex of the Hosting Zone in our Route53. So, say, the domain is example.com and it's registered in AWS with the name servers - all well. I have created a CustomDomain in the Openshift cluster that works for all it's subdomains eg. www.example.com. This is thanks to a wildcard CNAME record that points all *.example.com queries to zhfsrc.example-com.test.plvo.p1.openshiftapps.com provided by the CustomDomain object:

apiVersion: managed.openshift.io/v1alpha1
kind: CustomDomain
metadata:
name: example-com
spec:

certificate:

name: example-com-tls

namespace: example

domain: example.com

scope: External

status:

conditions:

...

- lastProbeTime: '2022-04-13T16:11:33Z'

lastTransitionTime: '2022-04-13T16:11:33Z'

message: Custom Apps Domain (example.com) Is Ready

reason: Ready

status: 'True'

type: Ready

dnsRecord: '*.example-com.test.plvo.p1.openshiftapps.com.'

endpoint: zhfsrc.example-com.test.plvo.p1.openshiftapps.com

scope: ''

state: Ready

Now, I am missing the A record and this breaks the deal. Restrictions found:

• the apex domain cannot be a CNAME
• the A record in Route53 cannot point to a CNAME
• there is (apparently) no resource the A record can be an alias for (tried the openshift LBs)
• CNAME flattening is not available in Route53

I see this as a most basic use case - a domain registered via AWS pointing to an Openshift application, yet neither RH nor AWS support were able to help so far.

I have a ConfigMap which stores Nginx configs and It is getting size exceeded. There are many site configs in there so I can't create multiple ConfigMaps.

I thought of using S3 to store ConfigMap, is it an option? If it is, how can one achieve it.

Why are you using the same rules for both parent and child pipelines? You are just triggering the child service if anything changes on files inside the child service directory So, just define rules on child pipeline... It will automatically trigger if any changes happen on service_a/*

I'm not sure whether this is a bug or not, so let me give somer background. Running in Vanilla 1.19.2, so no mods or anything. Not even a texture pack.

It's my understanding a command block needs a redstone signal to activate. However, it's also my understanding that a block can act as the 'activated' signal when next to a command block to start the impulse block.

However, it seems that in this 'indirect' method, it doesn't work with chains.

This may describe what I mean better:

A is the indirect chain, while B is the direct chain. The yellow wool in front of A1 will have a button on it, and B1 has a button directly on it.

A1 is configured to say Starting indirect chain.. B1 is configured to say Starting direct chain. Both A2 and B2 simply run say Chain 1 reached.

When I click the button directly on B1, it executes the entire chain as expected.

However, when I click the button on the block in front of A1, it should activate A1 and then A2 afterwards. However, it only executes A1. As seen below, it only executes the first block and nothing happens with the chain block behind it.

What baffles me is that, effectively, A1 has a redstone signal so it's my understanding this should chain to A2 and execute where it says the chain block command.

Am I misunderstanding how command blocks work, or is this a bug in 1.19.2?

You could use an item with knockback to knock it around, you can easily get such an item from the amazing command generator at mcstacker.net. you could use command blocks with /data to get a better result, but it is a lot of work.

For example:

/give @p cod{Enchantments:[{id:"minecraft:knockback",lvl:5s}]} 1

Give the slime regeneration so it doesn't die:

/effect give @e[type=slime,distance=..3,limit=1] regeneration 1000000 255